Opportunistic execution of secondary copy operations

ABSTRACT

Rather than relying on pre-defined scheduling of secondary copy operations such as backup jobs, the illustrative opportunistic approach initiates secondary copy operations based on changing operational conditions in a storage management system. An adaptive backup readiness score is based on a number of backup-readiness operational factors. An illustrative enhanced data agent which is associated with the target database application (or other executable component) may monitor the operational factors and determine the backup readiness score based on weights assigned to the respective operational factors. The enhanced data agent may evaluate recent backup jobs to determine which of the operational factors that contributed to the backup readiness score may have been most relevant. Based on the most-relevant analysis, the enhanced data agent may adapt the weights assigned to the monitored operational factors, so that the backup readiness score may be more suitable and responsive to ongoing operational conditions in the system.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.14/561,046, which was filed on Dec. 4, 2014 with the title of“Opportunistic Execution of Secondary Copy Operations.” Any and allapplications, if any, for which a foreign or domestic priority claim isidentified in the Application Data Sheet of the present application arehereby incorporated by reference under 37 CFR 1.57.

BACKGROUND

Businesses worldwide recognize the commercial value of their data andseek reliable, cost-effective ways to protect the information stored ontheir computer networks while minimizing impact on productivity.Protecting information is often part of a routine scheduled process thatis performed within an organization. A company might back up criticalcomputing systems such as databases, file servers, web servers, and soon as part of a daily, weekly, or monthly maintenance schedule. Thecompany may similarly protect computing systems used by each of itsemployees, such as those used by an accounting department, marketingdepartment, engineering department, and so forth.

SUMMARY

One issue that arises with storage management systems that protectdatabase applications is the management of the transaction log file(s)which database applications automatically populate substantiallyconcurrently with the execution of database transactions. A transactionlog file may be one or more files (collectively “log file”) that capturetransaction information for a database application, so that in case of acatastrophic failure transactions may be replayed and the databaserestored. Thus, for example, every transaction (e.g., add, change, anddelete of database records) may be captured in a log file. Some databaseapplications accumulate all transaction entries into one consolidatedtransaction log file; others generate a unique file for eachtransaction. The log file may be stored to the same storage device asthe database itself, or to another storage device. The log file isgenerally not part of the database and may be separately safeguarded.Regardless of the actual format/location of the log file, the log fileneeds to be periodically backed up to protected media. Moreover, it isgenerally considered good practice to keep log files to a manageablesize between backups, so that in the event the database needs to berestored, a relatively small number of transactions would have to bere-run from the log file. Otherwise, restoring a database based on atoo-large log file would keep the database out of service for too long.

Consequently, it is generally good practice to back up transaction logfiles relatively frequently so that downtime for restore operations,should they become necessary, will be relatively short. The traditionalapproach is to schedule log file backup jobs, e.g., every hour, everyquarter-hour, etc., depending on the characteristics of the databaseapplication. For example, a high-volume business-critical databaseapplication may be supported by more frequent log file backups ascompared to a lower-volume counterpart. Typically, after the log filehas been backed up, the production log file—the one populated at leastin part by the database application—is truncated and then re-populatedby the database application until the next backup and truncation, and soon.

However, a regularly scheduled backup job may collide with a busyheavily loaded system and may take away precious resources that would bebetter employed in running the production environment; a less busy timemight be preferable. On the other hand, a regularly scheduled backup jobalso may be unnecessary if the target database application has generatedfew transactions since the preceding backup. For example, a databaseapplication may be busy serving search results and reports to users, yetmay have relatively few add, change, and delete transactions to berecorded in the log file, in which case a log file backup job may takeaway precious processing resources and may use up backup storage thatmay be better employed otherwise.

The present inventors devised an opportunistic approach to solve thiskind of issue in an illustrative storage management system. Rather thanrelying on pre-defined scheduling of secondary copy operations such asbackup jobs, the illustrative opportunistic approach initiates secondarycopy operations based on changing operational conditions in the storagemanagement system, as reflected in an adaptive backup readiness score. Anumber of backup-readiness operational factors are employed to thispurpose. An illustrative enhanced data agent which is associated withthe target database application may monitor the operational factors anddetermine the backup readiness score based on weights assigned to therespective operational factors. Some backup readiness scores may triggera log file backup job to be initiated, e.g., based on a score threshold.Thus, backup jobs are initiated based on the backup readiness scorerather than on a pre-defined schedule.

Examples of backup-readiness operational factors that may be monitoredby the enhanced data agent may include any one or more of the following,without limitation: (i) a measure of the amount of storage spaceoccupied by the log file; (ii) a measure of the amount of storage spaceoccupied by the log file since a preceding backup job was initiated;(iii) a number of log file entries generated since the preceding backupjob; (iv) a number of database application transactions executed sincethe preceding backup job was initiated; (v) a measure of elapsed timesince the preceding backup job was initiated; (vi) a measure of activityof the database application during a period of time; (vii) a measure ofusage of the primary storage device during a period of time; (viii) ameasure of usage, by the database application, of the primary storagedevice during a period of time; and (ix) a measure of usage of theclient computing device during a period of time. Also, vendor-specificand release-specific operational factors may be used as well. In a givenstorage management system, the backup readiness score may be based on acombination of some but not necessarily all these operational factors,each factor having its own weight parameter.

The backup readiness score is adaptive. The enhanced data agent mayevaluate recent log file backup jobs to determine which of theoperational factors that contributed to the backup readiness score mayhave been most relevant. Based on the most-relevant analysis, theenhanced data agent may adapt weights assigned to the monitoredoperational factors, e.g., increasing, decreasing, maintaining, so thatthe backup readiness score may be more suitable and responsive toongoing operational conditions in the storage management system.

Illustratively, a backup-readiness operational factor may become mostrelevant in a particular evaluation cycle when it most often (relativeto the other operational factors considered in the backup readinessscore) exceeded its pre-defined threshold when the backup jobs wereinitiated. A repeated over-threshold condition for a certain operationalfactor may indicate that the condition needs more attention goingforward, for example may need to be more heavily weighted in the backupreadiness score so that a backup job may be more likely to be initiatedas a result. An operational factor that often exceeds its threshold mayweigh more so that triggering of backup jobs more closely hews to thatoperational factor's behavior. As conditions change in the storagemanagement system (as reflected by the operational factors) the backupreadiness score may trigger backup jobs sooner or later as appropriate.Thus, based on the set of monitored operational factors and theirrespective adaptive weights, the illustrative data agent mayopportunistically initiate backup jobs that are more consistent withchanging system conditions than the regularly scheduled approach of theprior art.

The invention is not limited to the enhanced data agent performing themonitoring, evaluating, adjusting, and/or initiating; alternatively, anenhanced storage manager and/or media agent may perform some or all ofthese operations. Furthermore, the invention is not limited to databaseapplications; any executable component may benefit from theopportunistic approach described herein, including, for example, a filesystem, an operating system, a virtual machine, any other application.Likewise, the invention is not limited to protecting log files; any kindof file or data structure may also benefit from opportunistic secondarycopy operations, e.g., directories, databases, etc. The invention alsois not limited to backup jobs; any secondary copy operation may beopportunistically executed, which may include making archive copies,making reference copies, making a copy of a secondary copy, takingsnapshots, and/or lifecycle management operations and hierarchicalstorage management, etc., without limitation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2 is a block diagram illustrating some salient portions of astorage management system 200 for opportunistic execution of secondarycopy operations, according to an illustrative embodiment of the presentinvention.

FIG. 3 depicts some salient operations of a method 300 according to anillustrative embodiment of the present invention.

FIG. 4 depicts some salient sub-operations of block 305 in method 300.

FIG. 5 depicts some salient sub-operations of block 311 in method 300.

FIG. 6 depicts some salient sub-operations of block 313 in method 300.

DETAILED DESCRIPTION

Systems and methods are disclosed for opportunistic execution ofsecondary copy operations. Examples of such systems and methods aredescribed in further detail herein, in reference to FIGS. 2-6.Components and functionality for opportunistic execution of secondarycopy operations may be configured and/or incorporated into informationmanagement systems such as those described herein in FIGS. 1A-1H.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot afford to take the risk of losing criticaldata. Moreover, runaway data growth and other modern realities makeprotecting and managing data an increasingly difficult task. There istherefore a need for efficient, powerful, and user-friendly solutionsfor protecting and managing data.

Depending on the size of the organization, there are typically many dataproduction sources which are under the purview of tens, hundreds, oreven thousands of employees or other individuals. In the past,individual employees were sometimes responsible for managing andprotecting their data. A patchwork of hardware and software pointsolutions has been applied in other cases. These solutions were oftenprovided by different vendors and had limited or no interoperability.

Certain embodiments described herein provide systems and methods capableof addressing these and other shortcomings of prior approaches byimplementing unified, organization-wide information management. FIG. 1Ashows one such information management system 100, which generallyincludes combinations of hardware and software configured to protect andmanage data and metadata, which is generated and used by the variouscomputing devices in information management system 100. The organizationthat employs the information management system 100 may be a corporationor other business entity, non-profit organization, educationalinstitution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents and patent application publications assigned toCommVault Systems, Inc., each of which is hereby incorporated in itsentirety by reference herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,229,954, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations”;    -   U.S. Pat. Pub. No. 2009/0319534, entitled “Application-Aware and        Remote Single Instance Data Management”;    -   U.S. Pat. Pub. No. 2012/0150818, entitled “Client-Side        Repository in a Networked Deduplicated Storage System”; and    -   U.S. Pat. Pub. No. 2012/0150826, entitled “Distributed        Deduplicated Storage System”;    -   U.S. patent application Ser. No. 14/218,679, entitled “Efficient        Information Management Performed by a Client in the Absence of a        Storage Manager;”    -   U.S. patent application Ser. No. 14/271,302, entitled        “Information Management by a Media Agent in the Absence of        Communications with a Storage Manager;” and    -   U.S. patent application Ser. No. 14/271,311, entitled        “Information Management by a Media Agent in the Absence of        Communications with a Storage Manager”.

The information management system 100 can include a variety of differentcomputing devices. For instance, as will be described in greater detailherein, the information management system 100 can include one or moreclient computing devices 102 and secondary storage computing devices106.

Computing devices can include, without limitation, one or more:workstations, personal computers, desktop computers, or other types ofgenerally fixed computing systems such as mainframe computers andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Computingdevices can include servers, such as mail servers, file servers,database servers, and web servers.

In some cases, a computing device includes virtualized and/or cloudcomputing resources. For instance, one or more virtual machines may beprovided to the organization by a third-party cloud service vendor. Or,in some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine.

A virtual machine includes an operating system and associated virtualresources, and is hosted simultaneously with another operating system ona physical host computer (or host machine). A hypervisor (typicallysoftware, and also known in the art as a virtual machine monitor or avirtual machine manager or “VMM”) sits between the virtual machine andthe hardware of the physical host machine. One example of hypervisor asvirtualization software is ESX Server, by VMware, Inc. of Palo Alto,Calif.; other examples include Microsoft Virtual Server and MicrosoftWindows Server Hyper-V, both by Microsoft Corporation of Redmond, Wash.,and Sun xVM by Oracle America Inc. of Santa Clara, Calif. In someembodiments, the hypervisor may be firmware or hardware or a combinationof software and/or firmware and/or hardware.

The hypervisor provides to each virtual operating system virtualresources, such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or morevirtual disks. The hypervisor typically stores the data of virtual disksin files on the file system of the physical host machine, called virtualmachine disk files (in the case of VMware virtual servers) or virtualhard disk image files (in the case of Microsoft virtual servers). Forexample, VMware's ESX Server provides the Virtual Machine File System(VMFS) for the storage of virtual machine disk files. A virtual machinereads data from and writes data to its virtual disk much the same waythat an actual physical machine reads data from and writes data to anactual disk.

Examples of techniques for implementing information managementtechniques in a cloud computing environment are described in U.S. Pat.No. 8,285,681, which is incorporated by reference herein. Examples oftechniques for implementing information management techniques in avirtualized computing environment are described in U.S. Pat. No.8,307,177, also incorporated by reference herein.

The information management system 100 can also include a variety ofstorage devices, including primary storage devices 104 and secondarystorage devices 108, for example. Storage devices can generally be ofany suitable type including, without limitation, disk drives, hard-diskarrays, semiconductor memory (e.g., solid state storage devices),network attached storage (NAS) devices, tape libraries or othermagnetic, non-tape storage devices, optical media storage devices,DNA/RNA-based memory technology, combinations of the same, and the like.In some embodiments, storage devices can form part of a distributed filesystem. In some cases, storage devices are provided in a cloud (e.g., aprivate cloud or one operated by a third-party vendor). A storage devicein some cases comprises a disk array or portion thereof.

The illustrated information management system 100 includes one or moreclient computing device 102 having at least one application 110executing thereon, and one or more primary storage devices 104 storingprimary data 112. The client computing device(s) 102 and the primarystorage devices 104 may generally be referred to in some cases as aprimary storage subsystem 117. A computing device in an informationmanagement system 100 that has a data agent 142 installed and operatingon it is generally referred to as a client computing device 102 (or, inthe context of a component of the information management system 100simply as a “client”).

Depending on the context, the term “information management system” canrefer to generally all of the illustrated hardware and softwarecomponents. Or, in other instances, the term may refer to only a subsetof the illustrated components.

For instance, in some cases, the information management system 100generally refers to a combination of specialized components used toprotect, move, manage, manipulate, analyze, and/or process data andmetadata generated by the client computing devices 102. However, theinformation management system 100 in some cases does not include theunderlying components that generate and/or store the primary data 112,such as the client computing devices 102 themselves, the applications110 and operating system operating on the client computing devices 102,and the primary storage devices 104. As an example, “informationmanagement system” may sometimes refer to one or more of the followingcomponents and corresponding data structures: storage managers, dataagents, and media agents. These components will be described in furtherdetail below.

Client Computing Devices

There are typically a variety of sources in an organization that producedata to be protected and managed. As just one illustrative example, in acorporate environment such data sources can be employee workstations andcompany servers such as a mail server, a web server, a database server,a transaction server, or the like. In the information management system100, the data generation sources include the one or more clientcomputing devices 102.

The client computing devices 102 may include any of the types ofcomputing devices described above, without limitation, and in some casesthe client computing devices 102 are associated with one or more usersand/or corresponding user accounts, of employees or other individuals.

The information management system 100 generally addresses and handlesthe data management and protection needs for the data generated by theclient computing devices 102. However, the use of this term does notimply that the client computing devices 102 cannot be “servers” in otherrespects. For instance, a particular client computing device 102 may actas a server with respect to other devices, such as other clientcomputing devices 102. As just a few examples, the client computingdevices 102 can include mail servers, file servers, database servers,and web servers.

Each client computing device 102 may have one or more applications 110(e.g., software applications) executing thereon which generate andmanipulate the data that is to be protected from loss and managed. Theapplications 110 generally facilitate the operations of an organization(or multiple affiliated organizations), and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file server applications, mail client applications (e.g., MicrosoftExchange Client), database applications (e.g., SQL, Oracle, SAP, LotusNotes Database), word processing applications (e.g., Microsoft Word),spreadsheet applications, financial applications, presentationapplications, graphics and/or video applications, browser applications,mobile applications, entertainment applications, and so on.

The client computing devices 102 can have at least one operating system(e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, otherUnix-based operating systems, etc.) installed thereon, which may supportor host one or more file systems and other applications 110.

The client computing devices 102 and other components in informationmanagement system 100 can be connected to one another via one or morecommunication pathways 114. For example, a first communication pathway114 may connect (or communicatively couple) client computing device 102and secondary storage computing device 106; a second communicationpathway 114 may connect storage manager 140 and client computing device102; and a third communication pathway 114 may connect storage manager140 and secondary storage computing device 106, etc. (see, e.g., FIG. 1Aand FIG. 1C). The communication pathways 114 can include one or morenetworks or other connection types including one or more of thefollowing, without limitation: the Internet, a wide area network (WAN),a local area network (LAN), a Storage Area Network (SAN), a FibreChannel connection, a Small Computer System Interface (SCSI) connection,a virtual private network (VPN), a token ring or TCP/IP based network,an intranet network, a point-to-point link, a cellular network, awireless data transmission system, a two-way cable system, aninteractive kiosk network, a satellite network, a broadband network, abaseband network, a neural network, a mesh network, an ad hoc network,other appropriate wired, wireless, or partially wired/wireless computeror telecommunications networks, combinations of the same or the like.The communication pathways 114 in some cases may also includeapplication programming interfaces (APIs) including, e.g., cloud serviceprovider APIs, virtual machine management APIs, and hosted serviceprovider APIs. The underlying infrastructure of communication paths 114may be wired and/or wireless, analog and/or digital, or any combinationthereof; and the facilities used may be private, public, third-partyprovided, or any combination thereof, without limitation.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 according to some embodiments is production data orother “live” data generated by the operating system and/or applications110 operating on a client computing device 102. The primary data 112 isgenerally stored on the primary storage device(s) 104 and is organizedvia a file system supported by the client computing device 102. Forinstance, the client computing device(s) 102 and correspondingapplications 110 may create, access, modify, write, delete, andotherwise use primary data 112. In some cases, some or all of theprimary data 112 can be stored in cloud storage resources (e.g., primarystorage device 104 may be a cloud-based resource).

Primary data 112 is generally in the native format of the sourceapplication 110. According to certain aspects, primary data 112 is aninitial or first (e.g., created before any other copies or before atleast one other copy) stored copy of data generated by the sourceapplication 110. Primary data 112 in some cases is created substantiallydirectly from data generated by the corresponding source applications110.

The primary storage devices 104 storing the primary data 112 may berelatively fast and/or expensive technology (e.g., a disk drive, ahard-disk array, solid state memory, etc.). In addition, primary data112 may be highly changeable and/or may be intended for relatively shortterm retention (e.g., hours, days, or weeks).

According to some embodiments, the client computing device 102 canaccess primary data 112 from the primary storage device 104 by makingconventional file system calls via the operating system. Primary data112 may include structured data (e.g., database files), unstructureddata (e.g., documents), and/or semi-structured data. Some specificexamples are described below with respect to FIG. 1B.

It can be useful in performing certain tasks to organize the primarydata 112 into units of different granularities. In general, primary data112 can include files, directories, file system volumes, data blocks,extents, or any other hierarchies or organizations of data objects. Asused herein, a “data object” can refer to both (1) any file that iscurrently addressable by a file system or that was previouslyaddressable by the file system (e.g., an archive file) and (2) a subsetof such a file (e.g., a data block).

As will be described in further detail, it can also be useful inperforming certain functions of the information management system 100 toaccess and modify metadata within the primary data 112. Metadatagenerally includes information about data objects or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to the metadata do not include the primary data.

Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists[ACLs]), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object.

In addition to metadata generated by or related to file systems andoperating systems, some of the applications 110 and/or other componentsof the information management system 100 maintain indices of metadatafor data objects, e.g., metadata associated with individual emailmessages. Thus, each data object may be associated with correspondingmetadata. The use of metadata to perform classification and otherfunctions is described in greater detail below.

Each of the client computing devices 102 are generally associated withand/or in communication with one or more of the primary storage devices104 storing corresponding primary data 112. A client computing device102 may be considered to be “associated with” or “in communication with”a primary storage device 104 if it is capable of one or more of: routingand/or storing data (e.g., primary data 112) to the particular primarystorage device 104, coordinating the routing and/or storing of data tothe particular primary storage device 104, retrieving data from theparticular primary storage device 104, coordinating the retrieval ofdata from the particular primary storage device 104, and modifyingand/or deleting data retrieved from the particular primary storagedevice 104.

The primary storage devices 104 can include any of the different typesof storage devices described above, or some other kind of suitablestorage device. The primary storage devices 104 may have relatively fastI/O times and/or are relatively expensive in comparison to the secondarystorage devices 108. For example, the information management system 100may generally regularly access data and metadata stored on primarystorage devices 104, whereas data and metadata stored on the secondarystorage devices 108 is accessed relatively less frequently.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102. For instance, a primary storage device 104 in oneembodiment is a local disk drive of a corresponding client computingdevice 102. In other cases, one or more primary storage devices 104 canbe shared by multiple client computing devices 102, e.g., via a networksuch as in a cloud storage implementation. As one example, a primarystorage device 104 can be a disk array shared by a group of clientcomputing devices 102, such as one of the following types of diskarrays: EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBMXIV, NetApp FAS, HP EVA, and HP 3PAR.

The information management system 100 may also include hosted services(not shown), which may be hosted in some cases by an entity other thanthe organization that employs the other components of the informationmanagement system 100. For instance, the hosted services may be providedby various online service providers to the organization. Such serviceproviders can provide services including social networking services,hosted email services, or hosted productivity applications or otherhosted applications). Hosted services may include software-as-a-service(SaaS), platform-as-a-service (PaaS), application service providers(ASPs), cloud services, or other mechanisms for delivering functionalityvia a network. As it provides services to users, each hosted service maygenerate additional data and metadata under management of theinformation management system 100, e.g., as primary data 112. In somecases, the hosted services may be accessed using one of the applications110. As an example, a hosted mail service may be accessed via browserrunning on a client computing device 102. The hosted services may beimplemented in a variety of computing environments. In some cases, theyare implemented in an environment having a similar arrangement to theinformation management system 100, where various physical and logicalcomponents are distributed over a network.

Secondary Copies and Exemplary Secondary Storage Devices

The primary data 112 stored on the primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112 during their normalcourse of work. Or the primary storage devices 104 can be damaged, lost,or otherwise corrupted. For recovery and/or regulatory compliancepurposes, it is therefore useful to generate copies of the primary data112. Accordingly, the information management system 100 includes one ormore secondary storage computing devices 106 and one or more secondarystorage devices 108 configured to create and store one or more secondarycopies 116 of the primary data 112 and associated metadata. Thesecondary storage computing devices 106 and the secondary storagedevices 108 may sometimes be referred to as a secondary storagesubsystem 118.

Creation of secondary copies 116 can help in search and analysis effortsand meet other information management goals, such as: restoring dataand/or metadata if an original version (e.g., of primary data 112) islost (e.g., by deletion, corruption, or disaster); allowingpoint-in-time recovery; complying with regulatory data retention andelectronic discovery (e-discovery) requirements; reducing utilizedstorage capacity; facilitating organization and search of data;improving user access to data files across multiple computing devicesand/or hosted services; and implementing data retention policies.

The client computing devices 102 access or receive primary data 112 andcommunicate the data, e.g., over one or more communication pathways 114,for storage in the secondary storage device(s) 108.

A secondary copy 116 can comprise a separate stored copy of applicationdata that is derived from one or more earlier-created, stored copies(e.g., derived from primary data 112 or another secondary copy 116).Secondary copies 116 can include point-in-time data, and may be intendedfor relatively long-term retention (e.g., weeks, months or years),before some or all of the data is moved to other storage or isdiscarded.

In some cases, a secondary copy 116 is a copy of application datacreated and stored subsequent to at least one other stored instance(e.g., subsequent to corresponding primary data 112 or to anothersecondary copy 116), in a different storage device than at least oneprevious stored copy, and/or remotely from at least one previous storedcopy. In some other cases, secondary copies can be stored in the samestorage device as primary data 112 and/or other previously storedcopies. For example, in one embodiment a disk array capable ofperforming hardware snapshots stores primary data 112 and creates andstores hardware snapshots of the primary data 112 as secondary copies116. Secondary copies 116 may be stored in relatively slow and/or lowcost storage (e.g., magnetic tape). A secondary copy 116 may be storedin a backup or archive format, or in some other format different thanthe native source application format or other primary data format.

In some cases, secondary copies 116 are indexed so users can browse andrestore at another point in time. After creation of a secondary copy 116representative of certain primary data 112, a pointer or other locationindicia (e.g., a stub) may be placed in primary data 112, or beotherwise associated with primary data 112 to indicate the currentlocation on the secondary storage device(s) 108 of secondary copy 116.

Since an instance of a data object or metadata in primary data 112 maychange over time as it is modified by an application 110 (or hostedservice or the operating system), the information management system 100may create and manage multiple secondary copies 116 of a particular dataobject or metadata, each representing the state of the data object inprimary data 112 at a particular point in time. Moreover, since aninstance of a data object in primary data 112 may eventually be deletedfrom the primary storage device 104 and the file system, the informationmanagement system 100 may continue to manage point-in-timerepresentations of that data object, even though the instance in primarydata 112 no longer exists.

For virtualized computing devices the operating system and otherapplications 110 of the client computing device(s) 102 may executewithin or under the management of virtualization software (e.g., a VMM),and the primary storage device(s) 104 may comprise a virtual diskcreated on a physical storage device. The information management system100 may create secondary copies 116 of the files or other data objectsin a virtual disk file and/or secondary copies 116 of the entire virtualdisk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 may be distinguished from corresponding primarydata 112 in a variety of ways, some of which will now be described.First, as discussed, secondary copies 116 can be stored in a differentformat (e.g., backup, archive, or other non-native format) than primarydata 112. For this or other reasons, secondary copies 116 may not bedirectly useable by the applications 110 of the client computing device102, e.g., via standard system calls or otherwise without modification,processing, or other intervention by the information management system100.

Secondary copies 116 are also in some embodiments stored on a secondarystorage device 108 that is inaccessible to the applications 110 runningon the client computing devices 102 (and/or hosted services). Somesecondary copies 116 may be “offline copies,” in that they are notreadily available (e.g., not mounted to tape or disk). Offline copiescan include copies of data that the information management system 100can access without human intervention (e.g., tapes within an automatedtape library, but not yet mounted in a drive), and copies that theinformation management system 100 can access only with at least somehuman intervention (e.g., tapes located at an offsite storage site).

The Use of Intermediate Devices for Creating Secondary Copies

Creating secondary copies can be a challenging task. For instance, therecan be hundreds or thousands of client computing devices 102 continuallygenerating large volumes of primary data 112 to be protected. Also,there can be significant overhead involved in the creation of secondarycopies 116. Moreover, secondary storage devices 108 may be specialpurpose components, and interacting with them can require specializedintelligence.

In some cases, the client computing devices 102 interact directly withthe secondary storage device 108 to create the secondary copies 116.However, in view of the factors described above, this approach cannegatively impact the ability of the client computing devices 102 toserve the applications 110 and produce primary data 112. Further, theclient computing devices 102 may not be optimized for interaction withthe secondary storage devices 108.

Thus, in some embodiments, the information management system 100includes one or more software and/or hardware components which generallyact as intermediaries between the client computing devices 102 and thesecondary storage devices 108. In addition to off-loading certainresponsibilities from the client computing devices 102, theseintermediate components can provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability.

The intermediate components can include one or more secondary storagecomputing devices 106 as shown in FIG. 1A and/or one or more mediaagents, which can be software modules operating on correspondingsecondary storage computing devices 106 (or other appropriate computingdevices). Media agents are discussed below (e.g., with respect to FIGS.1C-1E).

The secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,the secondary storage computing device(s) 106 include specializedhardware and/or software componentry for interacting with the secondarystorage devices 108.

To create a secondary copy 116 involving the copying of data from theprimary storage subsystem 117 to the secondary storage subsystem 118,the client computing device 102 in some embodiments communicates theprimary data 112 to be copied (or a processed version thereof) to thedesignated secondary storage computing device 106, via the communicationpathway 114. The secondary storage computing device 106 in turn conveysthe received data (or a processed version thereof) to the secondarystorage device 108. In some such configurations, the communicationpathway 114 between the client computing device 102 and the secondarystorage computing device 106 comprises a portion of a LAN, WAN or SAN.In other cases, at least some client computing devices 102 communicatedirectly with the secondary storage devices 108 (e.g., via Fibre Channelor SCSI connections). In some other cases, one or more secondary copies116 are created from existing secondary copies, such as in the case ofan auxiliary copy operation, described in greater detail below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view showing some specific examples of primarydata stored on the primary storage device(s) 104 and secondary copy datastored on the secondary storage device(s) 108, with other components inthe system removed for the purposes of illustration. Stored on theprimary storage device(s) 104 are primary data objects including wordprocessing documents 119A-B, spreadsheets 120, presentation documents122, video files 124, image files 126, email mailboxes 128 (andcorresponding email messages 129A-C), html/xml or other types of markuplanguage files 130, databases 132 and corresponding tables or other datastructures 133A-133C).

Some or all primary data objects are associated with correspondingmetadata (e.g., “Meta1-11”), which may include file system metadataand/or application specific metadata. Stored on the secondary storagedevice(s) 108 are secondary copy data objects 134A-C which may includecopies of or otherwise represent corresponding primary data objects andmetadata.

As shown, the secondary copy data objects 134A-C can individuallyrepresent more than one primary data object. For example, secondary copydata object 134A represents three separate primary data objects 133C,122, and 129C (represented as 133C′, 122′, and 129C′, respectively, andaccompanied by the corresponding metadata Meta11, Meta3, and Meta8,respectively). Moreover, as indicated by the prime mark (′), a secondarycopy object may store a representation of a primary data object and/ormetadata differently than the original format, e.g., in a compressed,encrypted, deduplicated, or other modified format. Likewise, secondarydata object 1346 represents primary data objects 120, 1336, and 119A as120′, 1336′, and 119A′, respectively and accompanied by correspondingmetadata Meta2, Meta10, and Meta1, respectively. Also, secondary dataobject 134C represents primary data objects 133A, 1196, and 129A as133A′, 1196′, and 129A′, respectively, accompanied by correspondingmetadata Meta9, Meta5, and Meta6, respectively.

Exemplary Information Management System Architecture

The information management system 100 can incorporate a variety ofdifferent hardware and software components, which can in turn beorganized with respect to one another in many different configurations,depending on the embodiment. There are critical design choices involvedin specifying the functional responsibilities of the components and therole of each component in the information management system 100. Forinstance, as will be discussed, such design choices can impactperformance as well as the adaptability of the information managementsystem 100 to data growth or other changing circumstances.

FIG. 1C shows an information management system 100 designed according tothese considerations and which includes: storage manager 140, acentralized storage and/or information manager that is configured toperform certain control functions, one or more data agents 142 executingon the client computing device(s) 102 configured to process primary data112, and one or more media agents 144 executing on the one or moresecondary storage computing devices 106 for performing tasks involvingthe secondary storage devices 108. While distributing functionalityamongst multiple computing devices can have certain advantages, in othercontexts it can be beneficial to consolidate functionality on the samecomputing device. As such, in various other embodiments, one or more ofthe components shown in FIG. 1C as being implemented on separatecomputing devices are implemented on the same computing device. In oneconfiguration, a storage manager 140, one or more data agents 142, andone or more media agents 144 are all implemented on the same computingdevice. In another embodiment, one or more data agents 142 and one ormore media agents 144 are implemented on the same computing device,while the storage manager 140 is implemented on a separate computingdevice, etc. without limitation.

Storage Manager

As noted, the number of components in the information management system100 and the amount of data under management can be quite large. Managingthe components and data is therefore a significant task, and a task thatcan grow in an often unpredictable fashion as the quantity of componentsand data scale to meet the needs of the organization. For these andother reasons, according to certain embodiments, responsibility forcontrolling the information management system 100, or at least asignificant portion of that responsibility, is allocated to the storagemanager 140. By distributing control functionality in this manner, thestorage manager 140 can be adapted independently according to changingcircumstances. Moreover, a computing device for hosting the storagemanager 140 can be selected to best suit the functions of the storagemanager 140. These and other advantages are described in further detailbelow with respect to FIG. 1D.

The storage manager 140 may be a software module or other application,which, in some embodiments operates in conjunction with one or moreassociated data structures, e.g., a dedicated database (e.g., managementdatabase 146). In some embodiments, storage manager 140 is a computingdevice comprising circuitry for executing computer instructions andperforms the functions described herein. The storage manager generallyinitiates, performs, coordinates and/or controls storage and otherinformation management operations performed by the informationmanagement system 100, e.g., to protect and control the primary data 112and secondary copies 116 of data and metadata. In general, storagemanager 100 may be said to manage information management system 100,which includes managing the constituent components, e.g., data agentsand media agents, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, the storage manager140 may communicate with and/or control some or all elements of theinformation management system 100, such as the data agents 142 and mediaagents 144. Thus, in certain embodiments, control information originatesfrom the storage manager 140 and status reporting is transmitted tostorage manager 140 by the various managed components, whereas payloaddata and payload metadata is generally communicated between the dataagents 142 and the media agents 144 (or otherwise between the clientcomputing device(s) 102 and the secondary storage computing device(s)106), e.g., at the direction of and under the management of the storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a taskassociated with an operation, data path information specifying whatcomponents to communicate with or access in carrying out an operation,and the like. Payload data, on the other hand, can include the actualdata involved in the storage operation, such as content data written toa secondary storage device 108 in a secondary copy operation. Payloadmetadata can include any of the types of metadata described herein, andmay be written to a storage device along with the payload content data(e.g., in the form of a header).

In other embodiments, some information management operations arecontrolled by other components in the information management system 100(e.g., the media agent(s) 144 or data agent(s) 142), instead of or incombination with the storage manager 140.

According to certain embodiments, the storage manager 140 provides oneor more of the following functions:

-   -   initiating execution of secondary copy operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   reporting, searching, and/or classification of data in the        information management system 100;    -   allocating secondary storage devices 108 for secondary storage        operations;    -   monitoring completion of and providing status reporting related        to secondary storage operations;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, and comparing the age information        against retention guidelines;    -   tracking movement of data within the information management        system 100;    -   tracking logical associations between components in the        information management system 100;    -   protecting metadata associated with the information management        system 100; and    -   implementing operations management functionality.

The storage manager 140 may maintain a database 146 (or “storage managerdatabase 146” or “management database 146”) of management-related dataand information management policies 148. The database 146 may include amanagement index 150 (or “index 150”) or other data structure thatstores logical associations between components of the system, userpreferences and/or profiles (e.g., preferences regarding encryption,compression, or deduplication of primary or secondary copy data,preferences regarding the scheduling, type, or other aspects of primaryor secondary copy or other operations, mappings of particularinformation management users or user accounts to certain computingdevices or other components, etc.), management tasks, mediacontainerization, or other useful data. For example, the storage manager140 may use the index 150 to track logical associations between mediaagents 144 and secondary storage devices 108 and/or movement of datafrom primary storage devices 104 to secondary storage devices 108. Forinstance, the index 150 may store data associating a client computingdevice 102 with a particular media agent 144 and/or secondary storagedevice 108, as specified in an information management policy 148 (e.g.,a storage policy, which is defined in more detail below).

Administrators and other people may be able to configure and initiatecertain information management operations on an individual basis. Butwhile this may be acceptable for some recovery operations or otherrelatively less frequent tasks, it is often not workable forimplementing on-going organization-wide data protection and management.Thus, the information management system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations (e.g., on an automated basis). Generally, aninformation management policy 148 can include a data structure or otherinformation source that specifies a set of parameters (e.g., criteriaand rules) associated with storage or other information managementoperations.

The storage manager database 146 may maintain the information managementpolicies 148 and associated data, although the information managementpolicies 148 can be stored in any appropriate location. For instance, aninformation management policy 148 such as a storage policy may be storedas metadata in a media agent database 152 or in a secondary storagedevice 108 (e.g., as an archive copy) for use in restore operations orother information management operations, depending on the embodiment.Information management policies 148 are described further below.

According to certain embodiments, the storage manager database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding data wereprotected). This and other metadata may additionally be stored in otherlocations, such as at the secondary storage computing devices 106 or onthe secondary storage devices 108, allowing data recovery without theuse of the storage manager 140 in some cases.

As shown, the storage manager 140 may include a jobs agent 156, a userinterface 158, and a management agent 154, all of which may beimplemented as interconnected software modules or application programs.

The jobs agent 156 in some embodiments initiates, controls, and/ormonitors the status of some or all storage or other informationmanagement operations previously performed, currently being performed,or scheduled to be performed by the information management system 100.For instance, the jobs agent 156 may access information managementpolicies 148 to determine when and how to initiate and control secondarycopy and other information management operations, as will be discussedfurther.

The user interface 158 may include information processing and displaysoftware, such as a graphical user interface (“GUI”), an applicationprogram interface (“API”), or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations (e.g., storage operations)or issue instructions to the information management system 100 and itsconstituent components. Via the user interface 158, users may optionallyissue instructions to the components in the information managementsystem 100 regarding performance of storage and recovery operations. Forexample, a user may modify a schedule concerning the number of pendingrations. As another example, a user may employ the GUI to view thestatus of pending storage operations or to monitor the status of certaincomponents in the information management system 100 (e.g., the amount ofcapacity left in a storage device).

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one client computingdevice 102 (comprising data agent(s) 142) and at least one media agent144. For instance, the components shown in FIG. 1C may together form aninformation management cell. Multiple cells may be organizedhierarchically. With this configuration, cells may inherit propertiesfrom hierarchically superior cells or be controlled by other cells inthe hierarchy (automatically or otherwise). Alternatively, in someembodiments, cells may inherit or otherwise be associated withinformation management policies, preferences, information managementmetrics, or other properties or characteristics according to theirrelative position in a hierarchy of cells. Cells may also be delineatedand/or organized hierarchically according to function, geography,architectural considerations, or other factors useful or desirable inperforming information management operations. A first cell may representa geographic segment of an enterprise, such as a Chicago office, and asecond cell may represent a different geographic segment, such as a NewYork office. Other cells may represent departments within a particularoffice. Where delineated by function, a first cell may perform one ormore first types of information management operations (e.g., one or morefirst types of secondary or other copies), and a second cell may performone or more second types of information management operations (e.g., oneor more second types of secondary or other copies).

The storage manager 140 may also track information that permits it toselect, designate, or otherwise identify content indices, deduplicationdatabases, or similar databases or resources or data sets within itsinformation management cell (or another cell) to be searched in responseto certain queries. Such queries may be entered by the user viainteraction with the user interface 158. In general, the managementagent 154 allows multiple information management cells to communicatewith one another. For example, the information management system 100 insome cases may be one information management cell of a network ofmultiple cells adjacent to one another or otherwise logically related ina WAN or LAN. With this arrangement, the cells may be connected to oneanother through respective management agents 154.

For instance, the management agent 154 can provide the storage manager140 with the ability to communicate with other components within theinformation management system 100 (and/or other cells within a largerinformation management system) via network protocols and applicationprogramming interfaces (“APIs”) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs. Inter-cell communication and hierarchy isdescribed in greater detail in e.g., U.S. Pat. Nos. 7,747,579 and7,343,453, which are incorporated by reference herein.

Data Agents

As discussed, a variety of different types of applications 110 canoperate on a given client computing device 102, including operatingsystems, database applications, e-mail applications, and virtualmachines, just to name a few. And, as part of the process of creatingand restoring secondary copies 116, the client computing devices 102 maybe tasked with processing and preparing the primary data 112 from thesevarious different applications 110. Moreover, the nature of theprocessing/preparation can differ across clients and application types,e.g., due to inherent structural and formatting differences amongapplications 110.

The one or more data agent(s) 142 are therefore advantageouslyconfigured in some embodiments to assist in the performance ofinformation management operations based on the type of data that isbeing protected, at a client-specific and/or application-specific level.

The data agent 142 may be a software module or component that isgenerally responsible for managing, initiating, or otherwise assistingin the performance of information management operations in informationmanagement system 100, generally as directed by storage manager 140. Forinstance, the data agent 142 may take part in performing data storageoperations such as the copying, archiving, migrating, and/or replicatingof primary data 112 stored in the primary storage device(s) 104. Thedata agent 142 may receive control information from the storage manager140, such as commands to transfer copies of data objects, metadata, andother payload data to the media agents 144.

In some embodiments, a data agent 142 may be distributed between theclient computing device 102 and storage manager 140 (and any otherintermediate components) or may be deployed from a remote location orits functions approximated by a remote process that performs some or allof the functions of data agent 142. In addition, a data agent 142 mayperform some functions provided by a media agent 144, or may performother functions such as encryption and deduplication.

As indicated, each data agent 142 may be specialized for a particularapplication 110, and the system can employ multiple application-specificdata agents 142, each of which may perform information managementoperations (e.g., perform backup, migration, and data recovery)associated with a different application 110. For instance, differentindividual data agents 142 may be designed to handle Microsoft Exchangedata, Lotus Notes data, Microsoft Windows file system data, MicrosoftActive Directory Objects data, SQL Server data, SharePoint data, Oracledatabase data, SAP database data, virtual machines and/or associateddata, and other types of data.

A file system data agent, for example, may handle data files and/orother file system information. If a client computing device 102 has twoor more types of data, a specialized data agent 142 may be used for eachdata type to copy, archive, migrate, and restore the client computingdevice 102 data. For example, to backup, migrate, and/or restore all ofthe data on a Microsoft Exchange server, the client computing device 102may use a Microsoft Exchange Mailbox data agent 142 to back up theExchange mailboxes, a Microsoft Exchange Database data agent 142 to backup the Exchange databases, a Microsoft Exchange Public Folder data agent142 to back up the Exchange Public Folders, and a Microsoft Windows FileSystem data agent 142 to back up the file system of the client computingdevice 102. In such embodiments, these specialized data agents 142 maybe treated as four separate data agents 142 even though they operate onthe same client computing device 102.

Other embodiments may employ one or more generic data agents 142 thatcan handle and process data from two or more different applications 110,or that can handle and process multiple data types, instead of or inaddition to using specialized data agents 142. For example, one genericdata agent 142 may be used to back up, migrate and restore MicrosoftExchange Mailbox data and Microsoft Exchange Database data while anothergeneric data agent may handle Microsoft Exchange Public Folder data andMicrosoft Windows File System data.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with the dataagent 142 and process the data as appropriate. For example, during asecondary copy operation, the data agent 142 may arrange or assemble thedata and metadata into one or more files having a certain format (e.g.,a particular backup or archive format) before transferring the file(s)to a media agent 144 or other component. The file(s) may include a listof files or other metadata. Each data agent 142 can also assist inrestoring data or metadata to primary storage devices 104 from asecondary copy 116. For instance, the data agent 142 may operate inconjunction with the storage manager 140 and one or more of the mediaagents 144 to restore data from secondary storage device(s) 108.

Media Agents

As indicated above with respect to FIG. 1A, off-loading certainresponsibilities from the client computing devices 102 to intermediatecomponents such as the media agent(s) 144 can provide a number ofbenefits including improved client computing device 102 operation,faster secondary copy operation performance, and enhanced scalability.In one specific example which will be discussed below in further detail,the media agent 144 can act as a local cache of copied data and/ormetadata that it has stored to the secondary storage device(s) 108,providing improved restore capabilities.

Generally speaking, a media agent 144 may be implemented as a softwaremodule that manages, coordinates, and facilitates the transmission ofdata, as directed by the storage manager 140, between a client computingdevice 102 and one or more secondary storage devices 108. Whereas thestorage manager 140 controls the operation of the information managementsystem 100, the media agent 144 generally provides a portal to secondarystorage devices 108. For instance, other components in the systeminteract with the media agents 144 to gain access to data stored on thesecondary storage devices 108, whether it be for the purposes ofreading, writing, modifying, or deleting data. Moreover, as will bedescribed further, media agents 144 can generate and store informationrelating to characteristics of the stored data and/or metadata, or cangenerate and store other types of information that generally providesinsight into the contents of the secondary storage devices 108.

Media agents 144 can comprise separate nodes in the informationmanagement system 100 (e.g., nodes that are separate from the clientcomputing devices 102, storage manager 140, and/or secondary storagedevices 108). In general, a node within the information managementsystem 100 can be a logically and/or physically separate component, andin some cases is a component that is individually addressable orotherwise identifiable. In addition, each media agent 144 may operate ona dedicated secondary storage computing device 106 in some cases, whilein other embodiments a plurality of media agents 144 operate on the samesecondary storage computing device 106.

A media agent 144 (and corresponding media agent database 152) may beconsidered to be “associated with” a particular secondary storage device108 if that media agent 144 is capable of one or more of: routing and/orstoring data to the particular secondary storage device 108,coordinating the routing and/or storing of data to the particularsecondary storage device 108, retrieving data from the particularsecondary storage device 108, coordinating the retrieval of data from aparticular secondary storage device 108, and modifying and/or deletingdata retrieved from the particular secondary storage device 108.

While media agent(s) 144 are generally associated with one or moresecondary storage devices 108, one or more media agents 144 in certainembodiments are physically separate from the secondary storage devices108. For instance, the media agents 144 may operate on secondary storagecomputing devices 106 having different housings or packages than thesecondary storage devices 108. In one example, a media agent 144operates on a first server computer and is in communication with asecondary storage device(s) 108 operating in a separate, rack-mountedRAID-based system.

Where the information management system 100 includes multiple mediaagents 144 (see, e.g., FIG. 1D), a first media agent 144 may providefailover functionality for a second, failed media agent 144. Inaddition, media agents 144 can be dynamically selected for storageoperations to provide load balancing. Failover and load balancing aredescribed in greater detail below.

In operation, a media agent 144 associated with a particular secondarystorage device 108 may instruct the secondary storage device 108 toperform an information management operation. For instance, a media agent144 may instruct a tape library to use a robotic arm or other retrievalmeans to load or eject a certain storage media, and to subsequentlyarchive, migrate, or retrieve data to or from that media, e.g., for thepurpose of restoring the data to a client computing device 102. Asanother example, a secondary storage device 108 may include an array ofhard disk drives or solid state drives organized in a RAIDconfiguration, and the media agent 144 may forward a logical unit number(LUN) and other appropriate information to the array, which uses thereceived information to execute the desired storage operation. The mediaagent 144 may communicate with a secondary storage device 108 via asuitable communications link, such as a SCSI or Fiber Channel link.

As shown, each media agent 144 may maintain an associated media agentdatabase 152. The media agent database 152 may be stored in a disk orother storage device (not shown) that is local to the secondary storagecomputing device 106 on which the media agent 144 operates. In othercases, the media agent database 152 is stored remotely from thesecondary storage computing device 106.

The media agent database 152 can include, among other things, an index153 (see, e.g., FIG. 1C), which comprises information generated duringsecondary copy operations and other storage or information managementoperations. The index 153 provides a media agent 144 or other componentwith a fast and efficient mechanism for locating secondary copies 116 orother data stored in the secondary storage devices 108. In some cases,the index 153 does not form a part of and is instead separate from themedia agent database 152.

A media agent index 153 or other data structure associated with theparticular media agent 144 may include information about the storeddata. For instance, for each secondary copy 116, the index 153 mayinclude metadata such as a list of the data objects (e.g.,files/subdirectories, database objects, mailbox objects, etc.), a pathto the secondary copy 116 on the corresponding secondary storage device108, location information indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, the index 153 includes metadata associated withthe secondary copies 116 that is readily available for use withouthaving to be first retrieved from the secondary storage device 108. Inyet further embodiments, some or all of the information in index 153 mayinstead or additionally be stored along with the secondary copies ofdata in a secondary storage device 108. In some embodiments, thesecondary storage devices 108 can include sufficient information toperform a “bare metal restore”, where the operating system of a failedclient computing device 102 or other restore target is automaticallyrebuilt as part of a restore operation.

Because the index 153 maintained in the media agent database 152 mayoperate as a cache, it can also be referred to as “an index cache.” Insuch cases, information stored in the index cache 153 typicallycomprises data that reflects certain particulars about storageoperations that have occurred relatively recently. After some triggeringevent, such as after a certain period of time elapses, or the indexcache 153 reaches a particular size, the index cache 153 may be copiedor migrated to a secondary storage device(s) 108. This information mayneed to be retrieved and uploaded back into the index cache 153 orotherwise restored to a media agent 144 to facilitate retrieval of datafrom the secondary storage device(s) 108. In some embodiments, thecached information may include format or containerization informationrelated to archives or other files stored on the storage device(s) 108.In this manner, the index cache 153 allows for accelerated restores.

In some alternative embodiments the media agent 144 generally acts as acoordinator or facilitator of storage operations between clientcomputing devices 102 and corresponding secondary storage devices 108,but does not actually write the data to the secondary storage device108. For instance, the storage manager 140 (or the media agent 144) mayinstruct a client computing device 102 and secondary storage device 108to communicate with one another directly. In such a case the clientcomputing device 102 transmits the data directly or via one or moreintermediary components to the secondary storage device 108 according tothe received instructions, and vice versa. In some such cases, the mediaagent 144 may still receive, process, and/or maintain metadata relatedto the storage operations. Moreover, in these embodiments, the payloaddata can flow through the media agent 144 for the purposes of populatingthe index cache 153 maintained in the media agent database 152, but notfor writing to the secondary storage device 108.

The media agent 144 and/or other components such as the storage manager140 may in some cases incorporate additional functionality, such as dataclassification, content indexing, deduplication, encryption,compression, and the like. Further details regarding these and otherfunctions are described below.

Distributed, Scalable Architecture

As described, certain functions of the information management system 100can be distributed amongst various physical and/or logical components inthe system. For instance, one or more of the storage manager 140, dataagents 142, and media agents 144 may operate on computing devices thatare physically separate from one another. This architecture can providea number of benefits.

For instance, hardware and software design choices for each distributedcomponent can be targeted to suit its particular function. The secondarycomputing devices 106 on which the media agents 144 operate can betailored for interaction with associated secondary storage devices 108and provide fast index cache operation, among other specific tasks.Similarly, the client computing device(s) 102 can be selected toeffectively service the applications 110 thereon, in order toefficiently produce and store primary data 112.

Moreover, in some cases, one or more of the individual components in theinformation management system 100 can be distributed to multiple,separate computing devices. As one example, for large file systems wherethe amount of data stored in the management database 146 is relativelylarge, the database 146 may be migrated to or otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of the storage manager 140. Thisdistributed configuration can provide added protection because thedatabase 146 can be protected with standard database utilities (e.g.,SQL log shipping or database replication) independent from otherfunctions of the storage manager 140. The database 146 can beefficiently replicated to a remote site for use in the event of adisaster or other data loss at the primary site. Or the database 146 canbe replicated to another computing device within the same site, such asto a higher performance machine in the event that a storage manager hostdevice can no longer service the needs of a growing informationmanagement system 100.

The distributed architecture also provides both scalability andefficient component utilization. FIG. 1D shows an embodiment of theinformation management system 100 including a plurality of clientcomputing devices 102 and associated data agents 142 as well as aplurality of secondary storage computing devices 106 and associatedmedia agents 144.

Additional components can be added or subtracted based on the evolvingneeds of the information management system 100. For instance, dependingon where bottlenecks are identified, administrators can add additionalclient computing devices 102, secondary storage computing devices 106(and corresponding media agents 144), and/or secondary storage devices108. Moreover, where multiple fungible components are available, loadbalancing can be implemented to dynamically address identifiedbottlenecks. As an example, the storage manager 140 may dynamicallyselect which media agents 144 and/or secondary storage devices 108 touse for storage operations based on a processing load analysis of themedia agents 144 and/or secondary storage devices 108, respectively.

Moreover, each client computing device 102 in some embodiments cancommunicate with, among other components, any of the media agents 144,e.g., as directed by the storage manager 140. And each media agent 144may be able to communicate with, among other components, any of thesecondary storage devices 108, e.g., as directed by the storage manager140. Thus, operations can be routed to the secondary storage devices 108in a dynamic and highly flexible manner, to provide load balancing,failover, and the like. Further examples of scalable systems capable ofdynamic storage operations, and of systems capable of performing loadbalancing and fail over are provided in U.S. Pat. No. 7,246,207, whichis incorporated by reference herein.

In alternative configurations, certain components are not distributedand may instead reside and execute on the same computing device. Forexample, in some embodiments, one or more data agents 142 and thestorage manager 140 operate on the same client computing device 102. Inanother embodiment, one or more data agents 142 and one or more mediaagents 144 operate on a single computing device.

Exemplary Types of Information Management Operations

In order to protect and leverage stored data, the information managementsystem 100 can be configured to perform a variety of informationmanagement operations. As will be described, these operations cangenerally include secondary copy and other data movement operations,processing and data manipulation operations, analysis, reporting, andmanagement operations. The operations described herein may be performedon any type of computing device, e.g., between two computers connectedvia a LAN, to a mobile client telecommunications device connected to aserver via a WLAN, to any manner of client computing device coupled to acloud storage target, etc., without limitation.

Data Movement Operations

Data movement operations according to certain embodiments are generallyoperations that involve the copying or migration of data (e.g., payloaddata) between different locations in the information management system100 in an original/native and/or one or more different formats. Forexample, data movement operations can include operations in which storeddata is copied, migrated, or otherwise transferred from one or morefirst storage devices to one or more second storage devices, such asfrom primary storage device(s) 104 to secondary storage device(s) 108,from secondary storage device(s) 108 to different secondary storagedevice(s) 108, from secondary storage devices 108 to primary storagedevices 104, or from primary storage device(s) 104 to different primarystorage device(s) 104.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication operations),snapshot operations, deduplication or single-instancing operations,auxiliary copy operations, and the like. As will be discussed, some ofthese operations involve the copying, migration or other movement ofdata, without actually creating multiple, distinct copies. Nonetheless,some or all of these operations are referred to as “copy” operations forsimplicity.

Backup Operations

A backup operation creates a copy of a version of data (e.g., one ormore files or other data units) in primary data 112 at a particularpoint in time. Each subsequent backup copy may be maintainedindependently of the first. Further, a backup copy in some embodimentsis generally stored in a form that is different than the native format,e.g., a backup format. This can be in contrast to the version in primarydata 112 from which the backup copy is derived, and which may instead bestored in a native format of the source application(s) 110. In variouscases, backup copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theoriginal application format. For example, a backup copy may be stored ina backup format that facilitates compression and/or efficient long-termstorage.

Backup copies can have relatively long retention periods as compared toprimary data 112, and may be stored on media with slower retrieval timesthan primary data 112 and certain other types of secondary copies 116.On the other hand, backups may have relatively shorter retention periodsthan some other types of secondary copies 116, such as archive copies(described below). Backups may sometimes be stored at an offsitelocation.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copy forsubsequent backup copies.

For instance, a differential backup operation (or cumulative incrementalbackup operation) tracks and stores changes that have occurred since thelast full backup. Differential backups can grow quickly in size, but canprovide relatively efficient restore times because a restore can becompleted in some cases using only the full backup copy and the latestdifferential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restore times can berelatively long in comparison to full or differential backups becausecompleting a restore operation may involve accessing a full backup inaddition to multiple incremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups, asynthetic full backup does not actually transfer data from a clientcomputer to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images, one for eachsubclient. The new backup images consolidate the index and user datastored in the related incremental, differential, and previous fullbackups, in some embodiments creating an archive file at the subclientlevel.

Any of the above types of backup operations can be at the volume-level,file-level, or block-level. Volume level backup operations generallyinvolve the copying of a data volume (e.g., a logical disk or partition)as a whole. In a file-level backup, the information management system100 may generally track changes to individual files, and includes copiesof files in the backup copy. In the case of a block-level backup, filesare broken into constituent blocks, and changes are tracked at theblock-level. Upon restore, the information management system 100reassembles the blocks into files in a transparent fashion.

Far less data may actually be transferred and copied to the secondarystorage devices 108 during a file-level copy than a volume-level copy.Likewise, a block-level copy may involve the transfer of less data thana file-level copy, resulting in faster execution times. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating constituent blocks can sometimes result in longerrestore times as compared to file-level backups. Similar to backupoperations, the other types of secondary copy operations describedherein can also be implemented at either the volume-level, file-level,or block-level.

For example, in some embodiments, a reference copy may comprisecopy(ies) of selected objects from backed up data, typically to helporganize data by keeping contextual information from multiple sourcestogether, and/or help retain specific data for a longer period of time,such as for legal hold needs. A reference copy generally maintains dataintegrity, and when the data is restored, it may be viewed in the sameformat as the source data. In some embodiments, a reference copy isbased on a specialized client, individual subclient and associatedinformation management policies (e.g., storage policy, retention policy,etc.) that are administered within information management system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied data in primary data 112 and also maintaining backup copies insecondary storage device(s) 108, they can consume significant storagecapacity. To help reduce storage consumption, an archive operationaccording to certain embodiments creates a secondary copy 116 by bothcopying and removing source data. Or, seen another way, archiveoperations can involve moving some or all of the source data to thearchive destination. Thus, data satisfying criteria for removal (e.g.,data of a threshold age or size) may be removed from source storage. Thesource data may be primary data 112 or a secondary copy 116, dependingon the situation. As with backup copies, archive copies can be stored ina format in which the data is compressed, encrypted, deduplicated,and/or otherwise modified from the format of the original application orsource copy. In addition, archive copies may be retained for relativelylong periods of time (e.g., years) and, in some cases, are neverdeleted. Archive copies are generally retained for longer periods oftime than backup copies, for example. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Moreover, when primary data 112 is archived, in some cases thecorresponding primary data 112 or a portion thereof is deleted whencreating the archive copy. Thus, archiving can serve the purpose offreeing up space in the primary storage device(s) 104 and easing thedemand on computational resources on client computing device 102.Similarly, when a secondary copy 116 is archived, the secondary copy 116may be deleted, and an archive copy can therefore serve the purpose offreeing up space in secondary storage device(s) 108. In contrast, sourcecopies often remain intact when creating backup copies. Examples ofcompatible data archiving operations are provided in U.S. Pat. No.7,107,298, which is incorporated by reference herein.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of the primary data 112 at agiven point in time, and may include state and/or status informationrelative to an application that creates/manages the primary data 112. Inone embodiment, a snapshot may generally capture the directory structureof an object in primary data 112 such as a file or volume or other dataset at a particular moment in time and may also preserve file attributesand contents. A snapshot in some cases is created relatively quickly,e.g., substantially instantly, using a minimum amount of file space, butmay still function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation can be asnapshot operation where a target storage device (e.g., a primarystorage device 104 or a secondary storage device 108) performs thesnapshot operation in a self-contained fashion, substantiallyindependently, using hardware, firmware and/or software operating on thestorage device itself. For instance, the storage device may be capableof performing snapshot operations upon request, generally withoutintervention or oversight from any of the other components in theinformation management system 100. In this manner, hardware snapshotscan off-load other components of information management system 100 fromprocessing involved in snapshot creation and management.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, can be a snapshot operation in which one or more othercomponents in information management system 100 (e.g., client computingdevices 102, data agents 142, etc.) implement a software layer thatmanages the snapshot operation via interaction with the target storagedevice. For instance, the component executing the snapshot managementsoftware layer may derive a set of pointers and/or data that representsthe snapshot. The snapshot management software layer may then transmitthe same to the target storage device, along with appropriateinstructions for writing the snapshot.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that are able to map files and directories tospecific memory locations (e.g., to specific disk blocks) where the dataresides, as it existed at the particular point in time. For example, asnapshot copy may include a set of pointers derived from the file systemor from an application. In some other cases, the snapshot may be createdat the block-level, such that creation of the snapshot occurs withoutawareness of the file system. Each pointer points to a respective storeddata block, so that collectively, the set of pointers reflect thestorage location and state of the data object (e.g., file(s) orvolume(s) or data set(s)) at a particular point in time when thesnapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories are modified later on. Furthermore, when files are modified,typically only the pointers which map to blocks are copied, not theblocks themselves. In some embodiments, for example in the case of“copy-on-write” snapshots, when a block changes in primary storage, theblock is copied to secondary storage or cached in primary storage beforethe block is overwritten in primary storage, and the pointer to thatblock is changed to reflect the new location of that block. The snapshotmapping of file system data may also be updated to reflect the changedblock(s) at that particular point in time. In some other cases, asnapshot includes a full physical copy of all or substantially all ofthe data represented by the snapshot. Further examples of snapshotoperations are provided in U.S. Pat. No. 7,529,782, which isincorporated by reference herein.

A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Another type of secondary copy operation is a replication operation.Some types of secondary copies 116 are used to periodically captureimages of primary data 112 at particular points in time (e.g., backups,archives, and snapshots). However, it can also be useful for recoverypurposes to protect primary data 112 in a more continuous fashion, byreplicating the primary data 112 substantially as changes occur. In somecases a replication copy can be a mirror copy, for instance, wherechanges made to primary data 112 are mirrored or substantiallyimmediately copied to another location (e.g., to secondary storagedevice(s) 108). By copying each write operation to the replication copy,two storage systems are kept synchronized or substantially synchronizedso that they are virtually identical at approximately the same time.Where entire disk volumes are mirrored, however, mirroring can requiresignificant amount of storage space and utilizes a large amount ofprocessing resources.

According to some embodiments storage operations are performed onreplicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, backup or otherwise manipulate thereplication copies as if the data were the “live” primary data 112. Thiscan reduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, the information management system 100 can replicatesections of application data that represent a recoverable state ratherthan rote copying of blocks of data. Examples of compatible replicationoperations (e.g., continuous data replication) are provided in U.S. Pat.No. 7,617,262, which is incorporated by reference herein.

Deduplication/Single-Instancing Operations

Another type of data movement operation is deduplication orsingle-instance storage, which is useful to reduce the amount ofnon-primary data. For instance, some or all of the above-describedsecondary storage operations can involve deduplication in some fashion.New data is read, broken down into portions (e.g., sub-file levelblocks, files, etc.) of a selected granularity, compared with blocksthat are already in secondary storage, and only the new blocks arestored. Blocks that already exist are represented as pointers to thealready stored data.

In order to streamline the comparison process, the informationmanagement system 100 may calculate and/or store signatures (e.g.,hashes or cryptographically unique IDs) corresponding to the individualdata blocks in a database and compare the signatures instead ofcomparing entire data blocks. In some cases, only a single instance ofeach element is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication or single-instancingoperations can store more than one instance of certain data blocks, butnonetheless significantly reduce data redundancy. Depending on theembodiment, deduplication blocks can be of fixed or variable length.Using variable length blocks can provide enhanced deduplication byresponding to changes in the data stream, but can involve complexprocessing. In some cases, the information management system 100utilizes a technique for dynamically aligning deduplication blocks(e.g., fixed-length blocks) based on changing content in the datastream, as described in U.S. Pat. No. 8,364,652, which is incorporatedby reference herein.

The information management system 100 can perform deduplication in avariety of manners at a variety of locations in the informationmanagement system 100. For instance, in some embodiments, theinformation management system 100 implements “target-side” deduplicationby deduplicating data (e.g., secondary copies 116) stored in thesecondary storage devices 108. In some such cases, the media agents 144are generally configured to manage the deduplication process. Forinstance, one or more of the media agents 144 maintain a correspondingdeduplication database that stores deduplication information (e.g.,datablock signatures). Examples of such a configuration are provided inU.S. Pat. Pub. No. 2012/0150826, which is incorporated by referenceherein. Instead of or in combination with “target-side” deduplication,deduplication can also be performed on the “source-side” (or“client-side”), e.g., to reduce the amount of traffic between the mediaagents 144 and the client computing device(s) 102 and/or reduceredundant data stored in the primary storage devices 104. According tovarious implementations, one or more of the storage devices of thetarget-side and/or source-side of an operation can be cloud-basedstorage devices. Thus, the target-side and/or source-side deduplicationcan be cloud-based deduplication. In particular, as discussedpreviously, the storage manager 140 may communicate with othercomponents within the information management system 100 via networkprotocols and cloud service provider APIs to facilitate cloud-baseddeduplication/single instancing. Examples of such deduplicationtechniques are provided in U.S. Pat. Pub. No. 2012/0150818, which isincorporated by reference herein. Some other compatiblededuplication/single instancing techniques are described in U.S. Pat.Pub. Nos. 2006/0224846 and 2009/0319534, which are incorporated byreference herein.

Information Lifecycle Management and Hierarchical Storage ManagementOperations

In some embodiments, files and other data over their lifetime move frommore expensive, quick access storage to less expensive, slower accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation. A HSM operation is generally an operation for automaticallymoving data between classes of storage devices, such as betweenhigh-cost and low-cost storage devices. For instance, an HSM operationmay involve movement of data from primary storage devices 104 tosecondary storage devices 108, or between tiers of secondary storagedevices 108. With each tier, the storage devices may be progressivelyrelatively cheaper, have relatively slower access/restore times, etc.For example, movement of data between tiers may occur as data becomesless important over time.

In some embodiments, an HSM operation is similar to an archive operationin that creating an HSM copy may (though not always) involve deletingsome of the source data, e.g., according to one or more criteria relatedto the source data. For example, an HSM copy may include data fromprimary data 112 or a secondary copy 116 that is larger than a givensize threshold or older than a given age threshold and that is stored ina backup format.

Often, and unlike some types of archive copies, HSM data that is removedor aged from the source is replaced by a logical reference pointer orstub. The reference pointer or stub can be stored in the primary storagedevice 104 (or other source storage device, such as a secondary storagedevice 108) to replace the deleted source data and to point to orotherwise indicate the new location in a secondary storage device 108.

According to one example, files are generally moved between higher andlower cost storage depending on how often the files are accessed. When auser requests access to the HSM data that has been removed or migrated,the information management system 100 uses the stub to locate the dataand may make recovery of the data appear transparent, even though theHSM data may be stored at a location different from other source data.In this manner, the data appears to the user (e.g., in file systembrowsing windows and the like) as if it still resides in the sourcelocation (e.g., in a primary storage device 104). The stub may alsoinclude some metadata associated with the corresponding data, so that afile system and/or application can provide some information about thedata object and/or a limited-functionality version (e.g., a preview) ofthe data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., where the data is compressed, encrypted, deduplicated,and/or otherwise modified from the original native application format).In some cases, copies which involve the removal of data from sourcestorage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “on-linearchive copies”. On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies”. Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453, which is incorporated by referenceherein.

Auxiliary Copy and Disaster Recovery Operations

An auxiliary copy is generally a copy operation in which a copy iscreated of an existing secondary copy 116. For instance, an initialsecondary copy 116 may be generated using or otherwise be derived fromprimary data 112 (or other data residing in the secondary storagesubsystem 118), whereas an auxiliary copy is generated from the initialsecondary copy 116. Auxiliary copies can be used to create additionalstandby copies of data and may reside on different secondary storagedevices 108 than the initial secondary copies 116. Thus, auxiliarycopies can be used for recovery purposes if initial secondary copies 116become unavailable. Exemplary compatible auxiliary copy techniques aredescribed in further detail in U.S. Pat. No. 8,230,195, which isincorporated by reference herein.

The information management system 100 may also perform disaster recoveryoperations that make or retain disaster recovery copies, often assecondary, high-availability disk copies. The information managementsystem 100 may create secondary disk copies and store the copies atdisaster recovery locations using auxiliary copy or replicationoperations, such as continuous data replication technologies. Dependingon the particular data protection goals, disaster recovery locations canbe remote from the client computing devices 102 and primary storagedevices 104, remote from some or all of the secondary storage devices108, or both.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can be differentthan data movement operations in that they do not necessarily involvethe copying, migration or other transfer of data (e.g., primary data 112or secondary copies 116) between different locations in the system. Forinstance, data analysis operations may involve processing (e.g., offlineprocessing) or modification of already stored primary data 112 and/orsecondary copies 116. However, in some embodiments data analysisoperations are performed in conjunction with data movement operations.Some data analysis operations include content indexing operations andclassification operations which can be useful in leveraging the dataunder management to provide enhanced search and other features. Otherdata analysis operations such as compression and encryption can providedata reduction and security benefits, respectively.

Classification Operations/Content Indexing

In some embodiments, the information management system 100 analyzes andindexes characteristics, content, and metadata associated with theprimary data 112 and/or secondary copies 116. The content indexing canbe used to identify files or other data objects having pre-definedcontent (e.g., user-defined keywords or phrases, other keywords/phrasesthat are not defined by a user, etc.), and/or metadata (e.g., emailmetadata such as “to”, “from”, “cc”, “bcc”, attachment name, receivedtime, etc.).

The information management system 100 generally organizes and cataloguesthe results in a content index, which may be stored within the mediaagent database 152, for example. The content index can also include thestorage locations of (or pointer references to) the indexed data in theprimary data 112 or secondary copies 116, as appropriate. The resultsmay also be stored, in the form of a content index database orotherwise, elsewhere in the information management system 100 (e.g., inthe primary storage devices 104, or in the secondary storage device108). Such index data provides the storage manager 140 or anothercomponent with an efficient mechanism for locating primary data 112and/or secondary copies 116 of data objects that match particularcriteria.

For instance, search criteria can be specified by a user through userinterface 158 of the storage manager 140. In some cases, the informationmanagement system 100 analyzes data and/or metadata in secondary copies116 to create an “off-line” content index, without significantlyimpacting the performance of the client computing devices 102. Dependingon the embodiment, the system can also implement “on-line” contentindexing, e.g., of primary data 112. Examples of compatible contentindexing techniques are provided in U.S. Pat. No. 8,170,995, which isincorporated by reference herein.

One or more components can be configured to scan data and/or associatedmetadata for classification purposes to populate a database (or otherdata structure) of information, which can be referred to as a “dataclassification database” or a “metabase”. Depending on the embodiment,the data classification database(s) can be organized in a variety ofdifferent ways, including centralization, logical sub-divisions, and/orphysical sub-divisions. For instance, one or more centralized dataclassification databases may be associated with different subsystems ortiers within the information management system 100. As an example, theremay be a first centralized metabase associated with the primary storagesubsystem 117 and a second centralized metabase associated with thesecondary storage subsystem 118. In other cases, there may be one ormore metabases associated with individual components, e.g., clientcomputing devices 102 and/or media agents 144. In some embodiments, adata classification database (metabase) may reside as one or more datastructures within management database 146, or may be otherwiseassociated with storage manager 140.

In some cases, the metabase(s) may be included in separate database(s)and/or on separate storage device(s) from primary data 112 and/orsecondary copies 116, such that operations related to the metabase donot significantly impact performance on other components in theinformation management system 100. In other cases, the metabase(s) maybe stored along with primary data 112 and/or secondary copies 116. Filesor other data objects can be associated with identifiers (e.g., tagentries, etc.) in the media agent 144 (or other indices) to facilitatesearches of stored data objects. Among a number of other benefits, themetabase can also allow efficient, automatic identification of files orother data objects to associate with secondary copy or other informationmanagement operations (e.g., in lieu of scanning an entire file system).Examples of compatible metabases and data classification operations areprovided in U.S. Pat. Nos. 8,229,954 and 7,747,579, which areincorporated by reference herein.

Encryption Operations

The information management system 100 in some cases is configured toprocess data (e.g., files or other data objects, secondary copies 116,etc.), according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard [AES], Triple Data Encryption Standard[3-DES], etc.) to limit access and provide data security in theinformation management system 100. The information management system 100in some cases encrypts the data at the client level, such that theclient computing devices 102 (e.g., the data agents 142) encrypt thedata prior to forwarding the data to other components, e.g., beforesending the data to media agents 144 during a secondary copy operation.In such cases, the client computing device 102 may maintain or haveaccess to an encryption key or passphrase for decrypting the data uponrestore. Encryption can also occur when creating copies of secondarycopies, e.g., when creating auxiliary copies or archive copies. In yetfurther embodiments, the secondary storage devices 108 can implementbuilt-in, high performance hardware encryption.

Management and Reporting Operations

Certain embodiments leverage the integrated, ubiquitous nature of theinformation management system 100 to provide useful system-widemanagement and reporting functions. Examples of some compatiblemanagement and reporting techniques are provided in U.S. Pat. No.7,343,453, which is incorporated by reference herein.

Operations management can generally include monitoring and managing thehealth and performance of information management system 100 by, withoutlimitation, performing error tracking, generating granularstorage/performance metrics (e.g., job success/failure information,deduplication efficiency, etc.), generating storage modeling and costinginformation, and the like. As an example, a storage manager 140 or othercomponent in the information management system 100 may analyze trafficpatterns and suggest and/or automatically route data via a particularroute to minimize congestion. In some embodiments, the system cangenerate predictions relating to storage operations or storage operationinformation. Such predictions, which may be based on a trendinganalysis, may predict various network operations or resource usage, suchas network traffic levels, storage media use, use of bandwidth ofcommunication links, use of media agent components, etc. Furtherexamples of traffic analysis, trend analysis, prediction generation, andthe like are described in U.S. Pat. No. 7,343,453, which is incorporatedby reference herein.

In some configurations, a master storage manager 140 may track thestatus of storage operation cells in a hierarchy, such as the status ofjobs, system components, system resources, and other items, bycommunicating with storage managers 140 (or other components) in therespective storage operation cells. Moreover, the master storage manager140 may track the status of its associated storage operation cells andinformation management operations by receiving periodic status updatesfrom the storage managers 140 (or other components) in the respectivecells regarding jobs, system components, system resources, and otheritems. In some embodiments, a master storage manager 140 may storestatus information and other information regarding its associatedstorage operation cells and other system information in its index 150(or other location).

The master storage manager 140 or other component may also determinewhether certain storage-related criteria or other criteria aresatisfied, and perform an action or trigger event (e.g., data migration)in response to the criteria being satisfied, such as where a storagethreshold is met for a particular volume, or where inadequate protectionexists for certain data. For instance, in some embodiments, data fromone or more storage operation cells is used to dynamically andautomatically mitigate recognized risks, and/or to advise users of risksor suggest actions to mitigate these risks. For example, an informationmanagement policy may specify certain requirements (e.g., that a storagedevice should maintain a certain amount of free space, that secondarycopies should occur at a particular interval, that data should be agedand migrated to other storage after a particular period, that data on asecondary volume should always have a certain level of availability andbe restorable within a given time period, that data on a secondaryvolume may be mirrored or otherwise migrated to a specified number ofother volumes, etc.). If a risk condition or other criterion istriggered, the system may notify the user of these conditions and maysuggest (or automatically implement) an action to mitigate or otherwiseaddress the risk. For example, the system may indicate that data from aprimary copy 112 should be migrated to a secondary storage device 108 tofree space on the primary storage device 104. Examples of the use ofrisk factors and other triggering criteria are described in U.S. Pat.No. 7,343,453, which is incorporated by reference herein.

In some embodiments, the system 100 may also determine whether a metricor other indication satisfies particular storage criteria and, if so,perform an action. For example, as previously described, a storagepolicy or other definition might indicate that a storage manager 140should initiate a particular action if a storage metric or otherindication drops below or otherwise fails to satisfy specified criteriasuch as a threshold of data protection. Examples of such metrics aredescribed in U.S. Pat. No. 7,343,453, which is incorporated by referenceherein.

In some embodiments, risk factors may be quantified into certainmeasurable service or risk levels for ease of comprehension. Forexample, certain applications and associated data may be considered tobe more important by an enterprise than other data and services.Financial compliance data, for example, may be of greater importancethan marketing materials, etc. Network administrators may assignpriority values or “weights” to certain data and/or applications,corresponding to the relative importance. The level of compliance ofstorage operations specified for these applications may also be assigneda certain value. Thus, the health, impact, and overall importance of aservice may be determined, such as by measuring the compliance value andcalculating the product of the priority value and the compliance valueto determine the “service level” and comparing it to certain operationalthresholds to determine whether it is acceptable. Further examples ofthe service level determination are provided in U.S. Pat. No. 7,343,453,which is incorporated by reference herein.

The system 100 may additionally calculate data costing and dataavailability associated with information management operation cellsaccording to an embodiment of the invention. For instance, data receivedfrom the cell may be used in conjunction with hardware-relatedinformation and other information about system elements to determine thecost of storage and/or the availability of particular data in thesystem. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular system pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453, which is incorporated by referenceherein.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via the userinterface 158 in a single, integrated view or console (not shown). Theconsole may support a reporting capability that allows for thegeneration of a variety of reports, which may be tailored to aparticular aspect of information management. Report types may include:scheduling, event management, media management and data aging. Availablereports may also include backup history, data aging history, auxiliarycopy history, job history, library and drive, media in library, restorehistory, and storage policy, etc., without limitation. Such reports maybe specified and created at a certain point in time as a systemanalysis, forecasting, or provisioning tool. Integrated reports may alsobe generated that illustrate storage and performance metrics, risks andstorage costing information. Moreover, users may create their ownreports based on specific needs.

The integrated user interface 158 can include an option to show a“virtual view” of the system that graphically depicts the variouscomponents in the system using appropriate icons. As one example, theuser interface 158 may provide a graphical depiction of one or moreprimary storage devices 104, the secondary storage devices 108, dataagents 142 and/or media agents 144, and their relationship to oneanother in the information management system 100. The operationsmanagement functionality can facilitate planning and decision-making.For example, in some embodiments, a user may view the status of some orall jobs as well as the status of each component of the informationmanagement system 100. Users may then plan and make decisions based onthis data. For instance, a user may view high-level informationregarding storage operations for the information management system 100,such as job status, component status, resource status (e.g.,communication pathways, etc.), and other information. The user may alsodrill down or use other means to obtain more detailed informationregarding a particular component, job, or the like. Further examples ofsome reporting techniques and associated interfaces providing anintegrated view of an information management system are provided in U.S.Pat. No. 7,343,453, which is incorporated by reference herein.

The information management system 100 can also be configured to performsystem-wide e-discovery operations in some embodiments. In general,e-discovery operations provide a unified collection and searchcapability for data in the system, such as data stored in the secondarystorage devices 108 (e.g., backups, archives, or other secondary copies116). For example, the information management system 100 may constructand maintain a virtual repository for data stored in the informationmanagement system 100 that is integrated across source applications 110,different storage device types, etc. According to some embodiments,e-discovery utilizes other techniques described herein, such as dataclassification and/or content indexing.

Information Management Policies

As indicated previously, an information management policy 148 caninclude a data structure or other information source that specifies aset of parameters (e.g., criteria and rules) associated with secondarycopy and/or other information management operations.

One type of information management policy 148 is a storage policy.According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following items: (1) what datawill be associated with the storage policy; (2) a destination to whichthe data will be stored; (3) datapath information specifying how thedata will be communicated to the destination; (4) the type of storageoperation to be performed; and (5) retention information specifying howlong the data will be retained at the destination (see, e.g., FIG. 1E).

As an illustrative example, data associated with a storage policy can belogically organized into groups. In some cases, these logical groupingscan be referred to as “sub-clients”. A sub-client may represent staticor dynamic associations of portions of a data volume. Sub-clients mayrepresent mutually exclusive portions. Thus, in certain embodiments, aportion of data may be given a label and the association is stored as astatic entity in an index, database or other storage location.Sub-clients may also be used as an effective administrative scheme oforganizing data according to data type, department within theenterprise, storage preferences, or the like. Depending on theconfiguration, sub-clients can correspond to files, folders, virtualmachines, databases, etc. In one exemplary scenario, an administratormay find it preferable to separate e-mail data from financial data usingtwo different sub-clients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the sub-clients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the sub-clients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesub-client data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria,which can be set forth in the storage policy. For instance, based onsuch criteria, a particular destination storage device(s) (or otherparameter of the storage policy) may be determined based oncharacteristics associated with the data involved in a particularstorage operation, device availability (e.g., availability of asecondary storage device 108 or a media agent 144), network status andconditions (e.g., identified bottlenecks), user credentials, and thelike).

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource (e.g., one or more host client computing devices 102) anddestination (e.g., a particular target secondary storage device 108).

A storage policy can also specify the type(s) of operations associatedwith the storage policy, such as a backup, archive, snapshot, auxiliarycopy, or the like. Retention information can specify how long the datawill be kept, depending on organizational needs (e.g., a number of days,months, years, etc.)

Another type of information management policy 148 is a schedulingpolicy, which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations will takeplace. Scheduling policies in some cases are associated with particularcomponents, such as particular logical groupings of data associated witha storage policy (e.g., a sub-client), client computing device 102, andthe like. In one configuration, a separate scheduling policy ismaintained for particular logical groupings of data on a clientcomputing device 102. The scheduling policy specifies that those logicalgroupings are to be moved to secondary storage devices 108 every houraccording to storage policies associated with the respectivesub-clients.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via the user interface 158. However, this can be aninvolved process resulting in delays, and it may be desirable to begindata protection operations quickly, without awaiting human intervention.Thus, in some embodiments, the information management system 100automatically applies a default configuration to client computing device102. As one example, when one or more data agent(s) 142 are installed onone or more client computing devices 102, the installation script mayregister the client computing device 102 with the storage manager 140,which in turn applies the default configuration to the new clientcomputing device 102. In this manner, data protection operations canbegin substantially immediately. The default configuration can include adefault storage policy, for example, and can specify any appropriateinformation sufficient to begin data protection operations. This caninclude a type of data protection operation, scheduling information, atarget secondary storage device 108, data path information (e.g., aparticular media agent 144), and the like.

Other types of information management policies 148 are possible,including one or more audit (or security) policies. An audit policy is aset of preferences, rules and/or criteria that protect sensitive data inthe information management system 100. For example, an audit policy maydefine “sensitive objects” as files or objects that contain particularkeywords (e.g., “confidential,” or “privileged”) and/or are associatedwith particular keywords (e.g., in metadata) or particular flags (e.g.,in metadata identifying a document or email as personal, confidential,etc.). An audit policy may further specify rules for handling sensitiveobjects. As an example, an audit policy may require that a reviewerapprove the transfer of any sensitive objects to a cloud storage site,and that if approval is denied for a particular sensitive object, thesensitive object should be transferred to a local primary storage device104 instead. To facilitate this approval, the audit policy may furtherspecify how a secondary storage computing device 106 or other systemcomponent should notify a reviewer that a sensitive object is slated fortransfer.

Another type of information management policy 148 is a provisioningpolicy. A provisioning policy can include a set of preferences,priorities, rules, and/or criteria that specify how client computingdevices 102 (or groups thereof) may utilize system resources, such asavailable storage on cloud storage and/or network bandwidth. Aprovisioning policy specifies, for example, data quotas for particularclient computing devices 102 (e.g., a number of gigabytes that can bestored monthly, quarterly or annually). The storage manager 140 or othercomponents may enforce the provisioning policy. For instance, the mediaagents 144 may enforce the policy when transferring data to secondarystorage devices 108. If a client computing device 102 exceeds a quota, abudget for the client computing device 102 (or associated department) isadjusted accordingly or an alert may trigger.

While the above types of information management policies 148 have beendescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items the information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of copy 116 (e.g., type of secondary copy) and/or copy        format (e.g., snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        information management system 100.

Policies can additionally specify or depend on a variety of historicalor current criteria that may be used to determine which rules to applyto a particular data object, system component, or information managementoperation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.        Exemplary Storage Policy and Secondary Storage Operations

FIG. 1E includes a data flow diagram depicting performance of storageoperations by an embodiment of an information management system 100,according to an exemplary storage policy 148A. The informationmanagement system 100 includes a storage manger 140, a client computingdevice 102 having a file system data agent 142A and an email data agent142B operating thereon, a primary storage device 104, two media agents144A, 144B, and two secondary storage devices 108A, 108B: a disk library108A and a tape library 108B. As shown, the primary storage device 104includes primary data 112A, which is associated with a logical groupingof data associated with a file system, and primary data 112B, which isassociated with a logical grouping of data associated with email.Although for simplicity the logical grouping of data associated with thefile system is referred to as a file system sub-client, and the logicalgrouping of data associated with the email is referred to as an emailsub-client, the techniques described with respect to FIG. 1E can beutilized in conjunction with data that is organized in a variety ofother manners.

As indicated by the dashed box, the second media agent 144B and the tapelibrary 108B are “off-site”, and may therefore be remotely located fromthe other components in the information management system 100 (e.g., ina different city, office building, etc.). Indeed, “off-site” may referto a magnetic tape located in storage, which must be manually retrievedand loaded into a tape drive to be read. In this manner, informationstored on the tape library 108B may provide protection in the event of adisaster or other failure.

The file system sub-client and its associated primary data 112A incertain embodiments generally comprise information generated by the filesystem and/or operating system of the client computing device 102, andcan include, for example, file system data (e.g., regular files, filetables, mount points, etc.), operating system data (e.g., registries,event logs, etc.), and the like. The e-mail sub-client, on the otherhand, and its associated primary data 112B, include data generated by ane-mail application operating on the client computing device 102, and caninclude mailbox information, folder information, emails, attachments,associated database information, and the like. As described above, thesub-clients can be logical containers, and the data included in thecorresponding primary data 112A, 1126 may or may not be storedcontiguously.

The exemplary storage policy 148A includes backup copy preferences (orrule set) 160, disaster recovery copy preferences rule set 162, andcompliance copy preferences or rule set 164. The backup copy rule set160 specifies that it is associated with a file system sub-client 166and an email sub-client 168. Each of these sub-clients 166, 168 areassociated with the particular client computing device 102. The backupcopy rule set 160 further specifies that the backup operation will bewritten to the disk library 108A, and designates a particular mediaagent 144A to convey the data to the disk library 108A. Finally, thebackup copy rule set 160 specifies that backup copies created accordingto the rule set 160 are scheduled to be generated on an hourly basis andto be retained for 30 days. In some other embodiments, schedulinginformation is not included in the storage policy 148A, and is insteadspecified by a separate scheduling policy.

The disaster recovery copy rule set 162 is associated with the same twosub-clients 166, 168. However, the disaster recovery copy rule set 162is associated with the tape library 108B, unlike the backup copy ruleset 160. Moreover, the disaster recovery copy rule set 162 specifiesthat a different media agent, namely 144B, will be used to convey thedata to the tape library 108B. As indicated, disaster recovery copiescreated according to the rule set 162 will be retained for 60 days, andwill be generated on a daily basis. Disaster recovery copies generatedaccording to the disaster recovery copy rule set 162 can provideprotection in the event of a disaster or other catastrophic data lossthat would affect the backup copy 116A maintained on the disk library108A.

The compliance copy rule set 164 is only associated with the emailsub-client 168, and not the file system sub-client 166. Compliancecopies generated according to the compliance copy rule set 164 willtherefore not include primary data 112A from the file system sub-client166. For instance, the organization may be under an obligation to storeand maintain copies of email data for a particular period of time (e.g.,10 years) to comply with state or federal regulations, while similarregulations do not apply to the file system data. The compliance copyrule set 164 is associated with the same tape library 108B and mediaagent 144B as the disaster recovery copy rule set 162, although adifferent storage device or media agent could be used in otherembodiments. Finally, the compliance copy rule set 164 specifies thatcopies generated under the compliance copy rule set 164 will be retainedfor 10 years, and will be generated on a quarterly basis.

At step 1, the storage manager 140 initiates a backup operationaccording to the backup copy rule set 160. For instance, a schedulingservice running on the storage manager 140 accesses schedulinginformation from the backup copy rule set 160 or a separate schedulingpolicy associated with the client computing device 102, and initiates abackup copy operation on an hourly basis. Thus, at the scheduled timeslot the storage manager 140 sends instructions to the client computingdevice 102 (i.e., to both data agent 142A and data agent 142B) to beginthe backup operation.

At step 2, the file system data agent 142A and the email data agent 142Boperating on the client computing device 102 respond to the instructionsreceived from the storage manager 140 by accessing and processing theprimary data 112A, 112B involved in the copy operation, which can befound in primary storage device 104. Because the operation is a backupcopy operation, the data agent(s) 142A, 142B may format the data into abackup format or otherwise process the data.

At step 3, the client computing device 102 communicates the retrieved,processed data to the first media agent 144A, as directed by the storagemanager 140, according to the backup copy rule set 160. In some otherembodiments, the information management system 100 may implement aload-balancing, availability-based, or other appropriate algorithm toselect from the available set of media agents 144A, 144B. Regardless ofthe manner the media agent 144A is selected, the storage manager 140 mayfurther keep a record in the storage manager database 146 of theassociation between the selected media agent 144A and the clientcomputing device 102 and/or between the selected media agent 144A andthe backup copy 116A.

The target media agent 144A receives the data from the client computingdevice 102, and at step 4 conveys the data to the disk library 108A tocreate the backup copy 116A, again at the direction of the storagemanager 140 and according to the backup copy rule set 160. The secondarystorage device 108A can be selected in other ways. For instance, themedia agent 144A may have a dedicated association with a particularsecondary storage device(s), or the storage manager 140 or media agent144A may select from a plurality of secondary storage devices, e.g.,according to availability, using one of the techniques described in U.S.Pat. No. 7,246,207, which is incorporated by reference herein.

The media agent 144A can also update its index 153 to include dataand/or metadata related to the backup copy 116A, such as informationindicating where the backup copy 116A resides on the disk library 108A,data and metadata for cache retrieval, etc. The storage manager 140 maysimilarly update its index 150 to include information relating to thestorage operation, such as information relating to the type of storageoperation, a physical location associated with one or more copiescreated by the storage operation, the time the storage operation wasperformed, status information relating to the storage operation, thecomponents involved in the storage operation, and the like. In somecases, the storage manager 140 may update its index 150 to include someor all of the information stored in the index 153 of the media agent144A. After the 30 day retention period expires, the storage manager 140instructs the media agent 144A to delete the backup copy 116A from thedisk library 108A. Indexes 150 and/or 153 are updated accordingly.

At step 5, the storage manager 140 initiates the creation of a disasterrecovery copy 116B according to the disaster recovery copy rule set 162.

At step 6, illustratively based on the instructions received from thestorage manager 140 at step 5, the specified media agent 144B retrievesthe most recent backup copy 116A from the disk library 108A.

At step 7, again at the direction of the storage manager 140 and asspecified in the disaster recovery copy rule set 162, the media agent144B uses the retrieved data to create a disaster recovery copy 116B onthe tape library 108B. In some cases, the disaster recovery copy 116B isa direct, mirror copy of the backup copy 116A, and remains in the backupformat. In other embodiments, the disaster recovery copy 116B may begenerated in some other manner, such as by using the primary data 112A,112B from the primary storage device 104 as source data. The disasterrecovery copy operation is initiated once a day and the disasterrecovery copies 1166 are deleted after 60 days; indexes are updatedaccordingly when/after each information management operation isexecuted/completed.

At step 8, the storage manager 140 initiates the creation of acompliance copy 116C, according to the compliance copy rule set 164. Forinstance, the storage manager 140 instructs the media agent 144B tocreate the compliance copy 116C on the tape library 108B at step 9, asspecified in the compliance copy rule set 164. In the example, thecompliance copy 116C is generated using the disaster recovery copy 116B.In other embodiments, the compliance copy 116C is instead generatedusing either the primary data 112B corresponding to the email sub-clientor using the backup copy 116A from the disk library 108A as source data.As specified, in the illustrated example, compliance copies 116C arecreated quarterly, and are deleted after ten years, and indexes are keptup-to-date accordingly.

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of the secondary copies116A, 1166, 116C. As one example, a user may manually initiate a restoreof the backup copy 116A by interacting with the user interface 158 ofthe storage manager 140. The storage manager 140 then accesses data inits index 150 (and/or the respective storage policy 148A) associatedwith the selected backup copy 116A to identify the appropriate mediaagent 144A and/or secondary storage device 108A.

In other cases, a media agent may be selected for use in the restoreoperation based on a load balancing algorithm, an availability basedalgorithm, or other criteria. The selected media agent 144A retrievesthe data from the disk library 108A. For instance, the media agent 144Amay access its index 153 to identify a location of the backup copy 116Aon the disk library 108A, or may access location information residing onthe disk 108A itself.

When the backup copy 116A was recently created or accessed, the mediaagent 144A accesses a cached version of the backup copy 116A residing inthe index 153, without having to access the disk library 108A for someor all of the data. Once it has retrieved the backup copy 116A, themedia agent 144A communicates the data to the source client computingdevice 102. Upon receipt, the file system data agent 142A and the emaildata agent 142B may unpackage (e.g., restore from a backup format to thenative application format) the data in the backup copy 116A and restorethe unpackaged data to the primary storage device 104.

Exemplary Applications of Storage Policies

The storage manager 140 may permit a user to specify aspects of thestorage policy 148A. For example, the storage policy can be modified toinclude information governance policies to define how data should bemanaged in order to comply with a certain regulation or businessobjective. The various policies may be stored, for example, in themanagement database 146. An information governance policy may comprise aclassification policy, which is described herein. An informationgovernance policy may align with one or more compliance tasks that areimposed by regulations or business requirements. Examples of informationgovernance policies might include a Sarbanes-Oxley policy, a HIPAApolicy, an electronic discovery (E-Discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on all of an organization's online and offline data,without the need for a dedicated data silo created solely for eachdifferent viewpoint. As described previously, the data storage systemsherein build a centralized index that reflects the contents of adistributed data set that spans numerous clients and storage devices,including both primary and secondary copies, and online and offlinecopies. An organization may apply multiple information governancepolicies in a top-down manner over that unified data set and indexingschema in order to permit an organization to view and manipulate thesingle data set through different lenses, each of which is adapted to aparticular compliance or business goal. Thus, for example, by applyingan E-discovery policy and a Sarbanes-Oxley policy, two different groupsof users in an organization can conduct two very different analyses ofthe same underlying physical set of data copies, which may bedistributed throughout the organization and information managementsystem.

A classification policy defines a taxonomy of classification terms ortags relevant to a compliance task and/or business objective. Aclassification policy may also associate a defined tag with aclassification rule. A classification rule defines a particularcombination of criteria, such as users who have created, accessed ormodified a document or data object; file or application types; contentor metadata keywords; clients or storage locations; dates of datacreation and/or access; review status or other status within a workflow(e.g., reviewed or un-reviewed); modification times or types ofmodifications; and/or any other data attributes in any combination,without limitation. A classification rule may also be defined usingother classification tags in the taxonomy. The various criteria used todefine a classification rule may be combined in any suitable fashion,for example, via Boolean operators, to define a complex classificationrule. As an example, an E-discovery classification policy might define aclassification tag “privileged” that is associated with documents ordata objects that (1) were created or modified by legal departmentstaff, or (2) were sent to or received from outside counsel via email,or (3) contain one of the following keywords: “privileged” or “attorney”or “counsel”, or other like terms.

One specific type of classification tag, which may be added to an indexat the time of indexing, is an entity tag. An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc.

A user may define a classification policy by indicating criteria,parameters or descriptors of the policy via a graphical user interface,such as a form or page with fields to be filled in, pull-down menus orentries allowing one or more of several options to be selected, buttons,sliders, hypertext links or other known user interface tools forreceiving user input, etc. For example, a user may define certain entitytags, such as a particular product number or project ID code that isrelevant in the organization. In some implementations, theclassification policy can be implemented using cloud-based techniques.For example, the storage devices may be cloud storage devices, and thestorage manager 140 may execute cloud service provider API over anetwork to classify data stored on cloud storage devices.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary, dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to a single secondary storage device 108 oracross multiple secondary storage devices 108. In some cases, users canselect different chunk sizes, e.g., to improve throughput to tapestorage devices.

Generally, each chunk can include a header and a payload. The payloadcan include files (or other data units) or subsets thereof included inthe chunk, whereas the chunk header generally includes metadata relatingto the chunk, some or all of which may be derived from the payload. Forexample, during a secondary copy operation, the media agent 144, storagemanager 140, or other component may divide the associated files intochunks and generate headers for each chunk by processing the constituentfiles. The headers can include a variety of information such as fileidentifier(s), volume(s), offset(s), or other information associatedwith the payload data items, a chunk sequence number, etc. Importantly,in addition to being stored with the secondary copy 116 on the secondarystorage device 108, the chunk headers can also be stored to the index153 of the associated media agent(s) 144 and/or the index 150. This isuseful in some cases for providing faster processing of secondary copies116 during restores or other operations. In some cases, once a chunk issuccessfully transferred to a secondary storage device 108, thesecondary storage device 108 returns an indication of receipt, e.g., tothe media agent 144 and/or storage manager 140, which may update theirrespective indexes 153, 150 accordingly. During restore, chunks may beprocessed (e.g., by the media agent 144) according to the information inthe chunk header to reassemble the files.

Data can also be communicated within the information management system100 in data channels that connect the client computing devices 102 tothe secondary storage devices 108. These data channels can be referredto as “data streams”, and multiple data streams can be employed toparallelize an information management operation, improving data transferrate, among providing other advantages. Example data formattingtechniques including techniques involving data streaming, chunking, andthe use of other data structures in creating copies (e.g., secondarycopies) are described in U.S. Pat. Nos. 7,315,923 and 8,156,086, and8,578,120, each of which is incorporated by reference herein.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing data storageoperations. Referring to FIG. 1F, the data agent 142 forms the datastream 170 from the data associated with a client computing device 102(e.g., primary data 112). The data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Thedata streams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (“SI”) data and/or non-SI data. Astream header 172 includes metadata about the stream payload 174. Thismetadata may include, for example, a length of the stream payload 174,an indication of whether the stream payload 174 is encrypted, anindication of whether the stream payload 174 is compressed, an archivefile identifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, the data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or fornon-SI data.

FIG. 1H is a diagram illustrating the data structures 180 that may beused to store blocks of SI data and non-SI data on the storage device(e.g., secondary storage device 108). According to certain embodiments,the data structures 180 do not form part of a native file system of thestorage device. The data structures 180 include one or more volumefolders 182, one or more chunk folders 184/185 within the volume folder182, and multiple files within the chunk folder 184. Each chunk folder184/185 includes a metadata file 186/187, a metadata index file 188/189,one or more container files 190/191/193, and a container index file192/194. The metadata file 186/187 stores non-SI data blocks as well aslinks to SI data blocks stored in container files. The metadata indexfile 188/189 stores an index to the data in the metadata file 186/187.The container files 190/191/193 store SI data blocks. The containerindex file 192/194 stores an index to the container files 190/191/193.Among other things, the container index file 192/194 stores anindication of whether a corresponding block in a container file190/191/193 is referred to by a link in a metadata file 186/187. Forexample, data block B2 in the container file 190 is referred to by alink in the metadata file 187 in the chunk folder 185. Accordingly, thecorresponding index entry in the container index file 192 indicates thatthe data block B2 in the container file 190 is referred to. As anotherexample, data block B1 in the container file 191 is referred to by alink in the metadata file 187, and so the corresponding index entry inthe container index file 192 indicates that this data block is referredto.

As an example, the data structures 180 illustrated in FIG. 1H may havebeen created as a result of two storage operations involving two clientcomputing devices 102. For example, a first storage operation on a firstclient computing device 102 could result in the creation of the firstchunk folder 184, and a second storage operation on a second clientcomputing device 102 could result in the creation of the second chunkfolder 185. The container files 190/191 in the first chunk folder 184would contain the blocks of SI data of the first client computing device102. If the two client computing devices 102 have substantially similardata, the second storage operation on the data of the second clientcomputing device 102 would result in the media agent 144 storingprimarily links to the data blocks of the first client computing device102 that are already stored in the container files 190/191. Accordingly,while a first storage operation may result in storing nearly all of thedata subject to the storage operation, subsequent storage operationsinvolving similar data may result in substantial data storage spacesavings, because links to already stored data blocks can be storedinstead of additional instances of data blocks.

If the operating system of the secondary storage computing device 106 onwhich the media agent 144 operates supports sparse files, then when themedia agent 144 creates container files 190/191/193, it can create themas sparse files. A sparse file is type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having the container files190/191/193 be sparse files allows the media agent 144 to free up spacein the container files 190/191/193 when blocks of data in the containerfiles 190/191/193 no longer need to be stored on the storage devices. Insome examples, the media agent 144 creates a new container file190/191/193 when a container file 190/191/193 either includes 100 blocksof data or when the size of the container file 190 exceeds 50 MB. Inother examples, the media agent 144 creates a new container file190/191/193 when a container file 190/191/193 satisfies other criteria(e.g., it contains from approximately 100 to approximately 1000 blocksor when its size exceeds approximately 50 MB to 1 GB).

In some cases, a file on which a storage operation is performed maycomprise a large number of data blocks. For example, a 100 MB file maycomprise 400 data blocks of size 256 KB. If such a file is to be stored,its data blocks may span more than one container file, or even more thanone chunk folder. As another example, a database file of 20 GB maycomprise over 40,000 data blocks of size 512 KB. If such a database fileis to be stored, its data blocks will likely span multiple containerfiles, multiple chunk folders, and potentially multiple volume folders.Restoring such files may require accessing multiple container files,chunk folders, and/or volume folders to obtain the requisite datablocks.

Opportunistic Execution of Secondary Copy Operations

FIG. 2 is a block diagram illustrating some salient portions of astorage management system 200 for opportunistic execution of secondarycopy operations, according to an illustrative embodiment of the presentinvention. Storage management system 200 is an enhanced embodiment of aninformation management system. System 200 may comprise: primary storagedevice 104 comprising log file 212 and database 213; secondary storagecomputing device 106 comprising media agent 144 and media agent database152; secondary storage device 108 comprising log file secondary copies216 (e.g., 216-1, 216-2, . . . , 216-n); storage manager 240; and clientcomputing device 202 comprising database application 210 and data agent242, which comprises opportunistic analysis module 243. The componentsmay be interconnected as shown by the double-sided arrows. The physicalcommunications infrastructure required to support these connections iswell known in the art and may be any suitable electronic communicationsinfrastructure, such as that described in regard to communicationpathways 114 above. System 200 may also comprise other components, suchas those illustrated in the preceding figures.

Primary storage device 104, secondary storage computing device 106,secondary storage device 108, media agent 144 and media agent database152 were described in detail above.

Client computing device 202 is analogous to client computing device 102described in detail above, and may further comprise additional featuresneeded to operate in system 200, e.g., data agent 242. Client computingdevice 202 may host one or more executable components, e.g., databaseapplication 210, another application, an operating system, a filesystem, an operating system, etc. When component 210 is a databaseapplication, client computing device 202 may be configured as a databaseserver. Client computing device 202 may also host corresponding dataagent(s), each data agent being associated with a respective executablecomponent, e.g., data agent 242, which is specially configured for andassociated with component 210.

Database application 210 is an executable component in the form of adatabase application, as is well known in the art. Examples of databaseapplication 210 may include Oracle, Microsoft SQL, DB2, etc. As is wellknown in the art, database applications typically track theirtransactions in a so-called log file or transaction log, which enablesthe database application to recover to a previous point in time and/orto replay the transactions. Database application 210 illustrativelypopulates and maintains a log file 212 and stores data in database 213.

Log file 212 is a primary data file, analogous to primary data 112 andstored in primary storage device 104, which comprises the transactionlog of database application 210. Log file 212 is considered to beprimary data, because it comprises data generated by databaseapplication 210 while it operates in “live” production mode. As databaseapplication 210 undergoes transactions, e.g., creating a new record,changing an existing record, deleting a record, etc., databaseapplication 210 tracks the particulars of each respective transaction inlog file 212 as is well known in the art. Depending on the vendor,configuration, and/or version of database application 210, log file 212may take different forms, such as a unitary file comprising thetransaction records, a collection of per-transaction files, a structuredindex file, and/or any combination thereof. In other words, log file 212may be embodied as one or more distinct files, but shall be referred toherein in the singular as “log file 212.” Log file 212 is populated atleast in part by database application 210.

When database application 210 experiences many transactions, which mayhappen when database 213 is very large, log file 212 may grow rapidly.Therefore, database operators generally desire to back up the log fileand then truncate it to a smaller size with better performancecharacteristics. Thus, secondary copies 216 of log file 212 may bestored to secondary storage, such as secondary storage device 108, e.g.,copy of log file 216-1, . . . , 216-n.

Database 213 is a primary data file that comprises the database datamanaged by database application 210. For example, database 213 maycomprise financial data, commercial transactions, emails, corporateinformation, etc., without limitation. Database 213 is considered to beprimary data, because it comprises data generated by databaseapplication 210 while it operates in “live” production mode. As databaseapplication 210 undergoes transactions, e.g., creating a new record,changing an existing record, deleting a record, etc., database 213stores these records as is well known in the art. Database 213 is shownhere co-residing with log file 212 on the same primary storage device104, but they may reside on separate storage devices, withoutlimitation. Log file 212 logs database 213 transactions as managed bydatabase application 210.

Log file (backup) copies 216 (e.g., 216-1, 216-2, . . . , 216-n) aresecondary copies of log file 212, which are generated by system 200 inrespective secondary copy operations, e.g., generated by backup jobs.Any and all of these secondary copies may be appropriately processed,e.g., classified, deduplicated or single-instanced, compressed,encrypted, or any combination thereof, etc., without limitation to thepresent invention. Thus, a log file copy 216 may not be identical to theoriginal log file 212, but may be an appropriate representation thereof,according to the configuration(s) of system 200.

Storage manager 240 is analogous to storage manager 140 described indetail above, and may additionally comprise enhancements required tooperate within system 200, e.g., enhanced message set to/from data agent242; opportunistic analysis functionality, etc., without limitation.

Data agent 242 is analogous to data agent 142 described in detail above,and further comprises additional functionality for operating in system200, e.g., opportunistic analysis module 243, enhanced message setto/from storage manager 240, enhanced message set to/from media agent144, etc. Data agent 242 is associated with database application 210.

Opportunistic analysis module 243 is a functional component of dataagent 242, and may be implemented as executable software and/orfirmware, which executes on the underlying client computing device 202.When it executes according to the illustrative embodiment, module 243 islargely responsible for determining when to initiate a backup job of logfile 212 according to so-called “opportunistic” principles described infurther detail herein (see, e.g., method 300). Thus, opportunisticanalysis module 243 may comprise one or more of the followingfunctionality, without limitation:

-   -   Initializing default values for parameters such as factor        weights, various thresholds, evaluation period and/or evaluation        count N, etc.;    -   Executing one or more monitoring operations;    -   Determining the value of a backup readiness score and whether        the backup readiness score exceeds a threshold value; or meets        other criteria for initiating a secondary copy operation;    -   Initiating and executing secondary copy operation(s) based on        the backup readiness score, e.g., log file backup job(s),        database backup jobs, etc.;    -   Evaluating and adjusting weights, if appropriate, for the        plurality of operational factors used in a backup readiness        score, e.g., based on the evaluation period and/or evaluation        count N;    -   During monitoring, collecting factor-related data and analyzing        a plurality of backup-readiness operational factors, e.g., disk        space usage since last backup job; number of log files and/or        transactions executed since last backup job; elapsed time since        last backup job; current load on resources, such as database        application, CPU, disk, etc.; vendor and/or version-specific        parameters relative to database application 210 and/or log file        212 and/or database 213, etc.;    -   Applying respective factor weights to generate a backup        readiness score based on a plurality of monitored operational        factors;    -   Storing factor value(s) and their respective weights (as        collected above), which factored into initiating a backup job;    -   Initiating secondary copy operation, e.g., a log file backup        job, which may include instructing and interoperating with a        media agent (e.g., 144) and/or notifying a storage manager        (e.g., 240) of the pending and/or completed backup job if a        communicative connection is available and/or interoperating with        a storage manager (e.g., 240) that may manage the secondary copy        operation;    -   Completing a secondary copy operation, e.g., log file backup        job, including saving and storing job results;    -   Notifying a storage manager (e.g., 240) of job results when a        communicative connection becomes available;    -   Discovering the one or more operational factors that was/were        the most relevant when a set of executed secondary copy        operations (e.g., backup jobs) were initiated;    -   Increasing the weight assigned to the discovered most-relevant        operational factor(s);    -   Adjusting remaining other operational factors' respective        weights based on the preceding weight increase;    -   Preparing to apply the adjusted factor weights (increased,        decreased, etc.) in the next monitoring cycle.

Opportunistic analysis module 243 is shown herein as a distinctcomponent to ease understanding of the present disclosure, however,alternative embodiments are also possible within the scope of thepresent invention. Module 243 may be embodied as a unified module withindata agent 242, layered on existing data agent code, or may be a logicalconstruct whose functionality is distributed through one or more otherfunctional modules of the data agent, and/or in any combination thereof.In some alternative embodiments, module 243 may be distinct from dataagent 242 and/or may execute on another computing component that isphysically distinct from client computing device 202, such as on adedicated server that operates in conjunction with data agent 242, butwhich may or may not be a logical component of data agent 242.

Dotted arrows 1 and 2 depict logical data pathways. Arrow 1 indicatesthat log file 212 logs transactions as received from databaseapplication 210. Arrow 2 indicates that log file 212 may beopportunistically backed up, according to the illustrative embodiment,via data agent 242 and media agent 144, ultimately resulting in asecondary copy 216. More details are provided in subsequent figures.

FIG. 3 depicts some salient operations of a method 300 according to anillustrative embodiment of the present invention. Method 300 isperformed by one or more components of storage management system 200, asdescribed in further detail below.

At block 301, storage manager 240 may administer, for each applicableclient (e.g., database application clients), an option for opportunisticexecution of log file backup jobs. A “client” is a logical component ofsystem 200, which may represent a logical grouping of one or more agentsinstalled on a client computing device 202, such as data agent 242 (insome embodiments, also including media agent 144 when installed onclient computing device 202). Storage manager 240 may recognize a clientas a component of system 200, and in some embodiments, may automaticallycreate a client component the first time a data agent (e.g., data agent242) is installed on a client computing device 202. Because datagenerated by database application 210 is tracked by the associated dataagent 242 so that it may be properly protected in system 200, a clientmay be said to generate data (e.g., transaction log entries, databaserecords, etc.) and to store the generated data to primary storage suchas to log file 212. According to the illustrative embodiment, anadministrable parameter of a client comprising data agent 242 may bewhether to use the opportunistic scheme disclosed herein for generatingsecondary copies of file 212. The administration may be by default, byscript, or by a user-administrator, without limitation.

At block 303, data agent 242 may initialize a number of default values.According to the illustrative embodiment, a number of parameters areused in the opportunistic execution scheme disclosed herein. Theseparameters may be initialized here with default values. These parametersmay include, without limitation:

-   -   Weights W1-W5 for respective backup-readiness operational        factors 401-405; a weight W is a relative number (e.g., a        percentage) applied to a corresponding operational factor in        calculating the backup readiness score, as described in more        detail in a subsequent figure. Initially, weights W1-W5 may        default to equal values, e.g., 20% each;    -   Threshold values for respective operational factors 401-405 are        discussed in more detail in a subsequent figure. For example, a        threshold value for the storage space usage factor 401 may be        initialized at 70% of allocated space; a threshold value for the        number of log files/transactions factor 402 may be initialized        at 100; a threshold value for the elapsed time threshold for        factor 403 may be initialized at 24 hours; a threshold value for        one of the load factors may be initialized at 30% CPU        utilization. Threshold values and default values may differ        according to the implementation of system 200, and furthermore,        may differ from one target file to another in the same system.    -   The illustrative operational factors 401-405 and their        corresponding weights W1-W5 may be adjusted, illustratively        after an evaluation period/evaluation count N. The evaluation        period may be a period of time, e.g., daily, two days, etc. The        evaluation count N may keep track of how many backup jobs have        occurred and trigger evaluation after N backup jobs, e.g., 10        backup jobs, 20 backup jobs, etc.

Other operational factors may be configured in addition to theillustrative ones shown above, without limitation. See also FIG. 4.

At block 305, data agent 242 (e.g., using opportunistic analysis module243) may execute monitoring operations during which time data agent 242monitors a number of operational factors and generates a backupreadiness score, as described in more detail in a subsequent figure.

At block 309, which is a decision point, data agent 242 may determinewhether backup readiness score (generated at block 305) exceeds acertain readiness threshold. When the backup readiness score exceeds thereadiness threshold, control passes to block 311. On the other hand,when the backup readiness score does not pass the threshold, monitoringoperations continue and control passes back to block 305. Anyappropriate value may be established for the backup readiness threshold,e.g., initialized at block 303, such as a value of 100. The thresholdvalue may vary according to the needs of system 200's operators and alsoaccording to the system's configuration. In some alternativeembodiments, data agent 242 may determine whether the backup readinessscore meets other criteria for initiating a secondary copy operation.

At block 311, data agent 242 may initiate a secondary copy operation,e.g., a log file backup job, based on the backup readiness score atblock 309. Here, a secondary copy of log file 212 is generated (e.g.,copy 216) and stored to secondary storage (e.g., secondary storagedevice 108). More details are provided in a subsequent figure.

At block 313, data agent 242 may evaluate and adjust weights W1-W5 forthe plurality of operational factors 401-405, based on an evaluationperiod/evaluation count N. After the evaluation period and/or evaluationcount N has elapsed, system 200 may enter an adaptive phase, asdescribed in more detail in a subsequent figure. Control may then passback to block 305 to resume monitoring operations, this time accordingto potentially different weights W1-W5. Alternatively, method 300 mayend after block 313.

FIG. 4 depicts some salient sub-operations of block 305 in method 300.In general, block 305 is directed at data agent 242 executing monitoringoperations, including factor-related data collection and analysis of aplurality of backup-readiness operational factors, 401-405. FIG. 4depicts five illustrative operational factors 401-405, each one having acorresponding weight W1-W5, which is applied to generate a backupreadiness score at block 411. According to the illustrative embodiment,data agent 242 monitors these operational factors, generates the backupreadiness score, and determines whether to initiate a secondary copyoperation for log file 212, e.g., a backup job, based on the backupreadiness score (see, e.g., block 309).

Data agent 242 may monitor any number of operational factors, such as401-405, without limitation. The set of monitored operational factorsmay vary from one log file to another log file, even within the samesystem 200. Likewise, a weight associated with a given operationalfactor also may vary from one log file to another. Backup-readinessoperational factor(s) that data agent 242 may monitor relative to aparticular log file 212 may comprise any one or more of the following:

-   -   a measure of the amount of storage space occupied by the log        file;    -   (ii) a measure of the amount of storage space occupied by the        log file since a preceding backup job was initiated;    -   (iii) a number of log file entries generated since the preceding        backup job;    -   (iv) a number of database application transactions executed        since the preceding backup job was initiated;    -   (v) a measure of elapsed time since the preceding backup job was        initiated;    -   (vi) a measure of activity of the database application during a        period of time;    -   (vii) a measure of usage of the primary storage device during a        period of time;    -   (viii) a measure of usage, by the database application, of the        primary storage device during a period of time; and    -   (ix) a measure of usage of the client computing device during a        period of time.

The applicable period of time may be recent, e.g., the five (5) minutesimmediately preceding the present evaluation. Thus, for example,database application activity or disk access may be measured during theimmediately preceding five minutes to determine whether the applicationand/or primary-storage disk is relatively lightly loaded; a light loadmay favor executing a backup job so that the backup job may not undulyoverload the system; on the other hand, when the database application isvery busy and/or the disk is heavily accessed may not be a good time toadd a backup job to the system load. Another exemplary operationalfactor may be a vendor-specific parameter associated with at least oneof the primary storage device and/or the executable component such asdatabase application 210 (e.g., where the vendor may be thecreator/manufacturer/service provider/etc.) such as a limit on filesizes or on the number of secondary copies. Another example ofoperational factor(s) may be a version-specific parameter associatedwith the executable component such as database application 210, e.g., amaximum size allowed for a log file, etc.

In reference to factor 401, data agent 242 may monitor the amount ofdisk space used by log file 212 since the last log file backup job asagainst the amount of disk space allocated thereto. Data agent 242 mayfurther determine whether a predefined threshold has been exceeded,e.g., 70%. This may mean that log file 212 is approaching maximumallowed storage, and thus needs to be backed up and then truncated sothat transaction logging may continue. Illustratively, when thethreshold has been exceeded, block 411 is triggered.

In reference to factor 402, data agent 242 may monitor the number of logfiles generated since the last backup job (in some configurations)and/or may monitor the number of transactions that have been enteredinto log file 212 since the last backup job. Data agent 242 may furtherdetermine whether this exceeds a pre-defined threshold, e.g., 100files/transactions. This may mean that after a certain number oftransactions it may be time to back up log file 212 and truncate it sothat transaction logging may continue. Illustratively, when thethreshold has been exceeded, block 411 is triggered.

In reference to factor 403, data agent 242 may determine whether apredefined amount of time has elapsed since the last log file backupjob, e.g., 24 hours. Illustratively, when the threshold has beenexceeded, block 411 is triggered. This factor is useful in ensuring thatlog file 212 is backed up occasionally, even if database application 210operations do not trigger some of the other factors and their respectivethresholds. For example, the present factor ensures that, at a minimum,a backup readiness score is generated daily, which may in turn cause abackup job to be executed for log file 212.

In reference to factor 404, data agent 242 may monitor one or morecurrent resources (e.g., database, disk, CPU) to determine whether theyare lightly loaded, so that executing a backup job would be less likelyto overload system components. Illustratively, when an applicablethreshold has been exceeded, block 411 may be triggered. For example,data agent 242 may monitor database application 210 to determine whetherit is busy relative to other times of day, e.g., executing fewer than 50transactions per minute. Data agent 242 may also monitor CPU usage onclient computing device 202 (e.g., database server), e.g., to determinewhether it operates at less than 30% load. Data agent 242 also maymonitor access (e.g., reads, writes) to primary storage device 104(e.g., to/from database 213), e.g., accessing fewer than 500 records perminute. These thresholds are exemplary to illustrate how factor 404 maybe configured to favor launching a log file backup job in a lightlyloaded system for.

In reference to factor 405, data agent 242 may monitor specific vendorand/or version-specific parameters, which may be associated withdatabase application 210, primary storage device 104, and/or otheraspects of system 200, such as the number of data agents 242 and/ormedia agents 144 that may be operational. For example, fewer backup jobsmay be launched in a system 200 that comprises more data agents andfewer media agents, to avoid creating bottlenecks. Illustratively, whenan operational threshold has been exceeded, block 411 may be triggered.

Weights W1-W5 correspond to factors 401-405, respectively. When a backupreadiness score is generated at block 411, it is based on a weight W1-W5applied to its corresponding factor value resulting from the monitoringoperation. As explained elsewhere herein, the weights may be adjusted toadapt to system behavior over time (see, e.g., block 313). Initially,weights W1-W5 may default to co-equal values (see, e.g., block 303). Insome implementations of system 200, a weight W may be set to zero whenthe corresponding factor is irrelevant or undesirable as a driver forgenerating a backup readiness score and launching backup jobs. Forexample, factor 402 may be associated with a weight W2 set at zero, sothat factor 402 may drop out of backup readiness considerations; forinstance this may occur when the database application 210 generates onlyone log file 212 and when the number of transactions may not beavailable to data agent 242 and/or may correlate highly with the diskspace factor 401 and thus may become irrelevant.

At block 411, data agent 242 may generate a backup readiness score basedon the plurality of monitored factors. Block 411 may be triggered by anynumber of events, e.g., after a predefined time period; after athreshold associated with one or more factors 401-405 triggers block411, etc., without limitation.

An illustrative formula for the backup readiness score may be:

           Equation  1Illustrative  formula  for  Backup  Readiness  Score  (e.g., block  411)$\mspace{20mu}{{{Backup}\mspace{14mu}{Readiness}\mspace{14mu}{Score}} = {\sum\limits_{i = 1}^{n}{{normalized}\mspace{14mu}{factor}\mspace{14mu} 40n \times {weight}\mspace{14mu} W\; n}}}$E.g., Backup  Readiness  Score = normalized  factor  401 × W 1 + 402 × W 2 + 403 × W 3 + 404 × W 4 + 405 × W 5,          where  W 1-W 5 = 0%  …  100%

Since the operational factors refer to disparate concepts that may becharacterized in different ways and on different scales, normalizationmay be needed. For instance, a normalized measure of load lightnessaccording to factor 404 may be (1−CPU usage %), with an illustrativethreshold of 59%. An example of this and other factors appears in Table1 below. Because implementations and configurations vary significantlyamong systems, aspects of the illustrative formula may be administeredaccordingly. As noted, this may be done by a user-administrator and/orvia scripting. Block 305 may end here and control may pass to block 309.

FIG. 5 depicts some salient sub-operations of block 311 in method 300.

In general, block 311 is directed at data agent 242 initiating andexecuting a log file backup job for log file 212—based on the backupreadiness score at block 309. Because it is based on the backupreadiness score instead of being based on a predefined schedule, the logfile backup job is said to be opportunistic. Rather than initiating abackup job based on a predefined schedule, the opportunistic backup jobhere is launched based on the backup readiness score resulting from theinteraction of a plurality of factors and their respective weights.

At block 501, data agent 242 and/or storage manager 240 may store factorvalue(s) and respective weights (e.g., collected at block 305), whichfactored into the backup readiness score that triggered the presentbackup job. The reason for saving and storing these figures is that theymay be analyzed in a later evaluation at block 313. These figures may bestored illustratively in a data structure maintained by data agent 242,e.g. a local cache, a file in primary storage device 104, etc.

At block 503, data agent 242 may initiate a log file backup job, e.g.,instruct and interoperate with a media agent (e.g., 144) to copy logfile 212 to a secondary copy 216. Data agent 242 may also notify thestorage manager (e.g., 240) if a communications connection is availablethereto; otherwise, communications to/from storage manager 240 may bedelayed until a later, more suitable time (see, e.g., block 509). Forexample, data agent 242 may arrange or assemble the data and metadata inlog file 212 into one or more files having a certain format (e.g., aparticular backup or archive format) before transferring the file(s) toa media agent 144 in the course of the backup job.

Data agent 242 may act independently of storage manager 240 at thispoint to initiate the backup job. For example, according to theillustrative embodiment, data agent 242 is the component that initiatesthe backup job, for example, communicating with an appropriate mediaagent such as media agent 144, rather than relying on the storagemanager to do the initiating and the job management. An illustrativeembodiment of this kind of independent action by a data agent isdescribed in U.S. patent application Ser. No. 14/218,679, entitled“Efficient Information Management Performed by a Client in the Absenceof a Storage Manager,” which is incorporated by reference herein.Another illustrative embodiment involving independent action absent acommunicative connection to the storage manager is described in U.S.patent application Ser. No. 14/271,302, entitled “Information Managementby a Media Agent in the Absence of Communications with a StorageManager,” and U.S. patent application Ser. No. 14/271,311 with the sametitle, both of which are also incorporated by reference herein. In somealternative embodiments, on the other hand, data agent 242 may notifystorage manager 240 that a backup readiness score exceeds itsoperational threshold; storage manager 240 may then take over controland initiate and manage a log file backup job, instead of data agent 242doing so.

At block 505, media agent 144 may receive the processed log file 212from data agent 242, and may further process it by indexing it andgenerating a secondary copy of the log file (e.g., 216-1, 216-2, etc.),which media agent 144 then stores to secondary storage device 108.Indexed information from this operation may be stored in media agentdatabase 152 and/or index cache 153.

At block 507, data agent 242 may complete the present backup job and maystore job results. Because it illustratively operates independently ofstorage manager 240 to manage the present log file backup job, dataagent 242 may manage the job, monitor the job, and collect appropriatejob results, e.g., error rates, completion status, etc. Job results maybe stored illustratively in a data structure maintained by data agent242, e.g. a local cache, a file in primary storage device 104, etc.

At block 509, data agent 242 may notify storage manager 240 of jobresults when a communicative connection is available. In configurationswhere communications between data agent 242 and storage manager 240 aresporadic and/or unreliable, data agent 242 may collect jobs metadata andjob results and report them to storage manager 240 at such time ascommunications are available. Block 311 may end here and control maypass to block 313.

FIG. 6 depicts some salient sub-operations of block 313 in method 300.In general, block 313 is directed at an adaptive process whereby dataagent 242 evaluates and adjusts weights for the plurality ofbackup-readiness factors, so that adjusted weights may be applied in thenext monitoring round or rounds. In the illustrative embodiment, thepresent evaluation block is governed by an evaluation parameter, whichmay be a period of time or a number of completed log file backup jobs,N. Upon the expiration of the evaluation parameter, e.g., every 3 days,every 10 backup jobs, etc., data agent 242 (e.g., using opportunisticanalysis module 243) may perform the operations of block 313.

At block 601, which is launched upon expiration of the evaluationparameter, e.g., after completion of N number of log file backup jobs,data agent 242 may perform the following operations.

At block 603, data agent 242 may discover the backup-readinessoperational factor that was “most relevant” in the set of preceding logfile backup jobs that occurred since the last evaluation, or possiblymore than one such factor. A most-relevant factor may be defined as thebackup-readiness factor which, among the set of evaluated backup jobs,most frequently exceeded its threshold. Since exceeding a thresholdkicks off a backup readiness score analysis (see, e.g., block 411), atleast one factor exceeds its threshold when a backup job is initiated asa result of the backup readiness score.

According to the illustrative embodiment, a backup-readiness operationalfactor that exceeds its threshold more frequently than other factors mayindicate that operational conditions are such that more backup jobs maybe appropriate to keep the factor from continuing to exceed thethreshold. To ameliorate these conditions according to the illustrativeapproach, a most-relevant factor should be more heavily weighted goingforward so that it may influence the backup readiness score more andpotentially cause more backup jobs to occur. In the longer term, then,this factor may be overtaken by another factor that exceeds itsrespective threshold more often in another evaluation period, becomesthe most-relevant factor, and receives a corresponding increase in itsweight relative to the other factors. Hence the adaptive nature of thepresent approach.

Thus, the present scheme of discovering most-relevant factors andincreasing their going-forward weights advantageously enables theillustrative system to adapt to changing conditions. Rather than relyingon fixed operational parameters, such as regularly scheduled backupsfound in the prior art, the present system opportunistically launchesbackup jobs based on a backup readiness score, which in turn istriggered by any one or more backup-readiness factors exceeding arespective threshold. As conditions change and different thresholdsbecome most-relevant, the system adapts by adjusting weights, which thenmay affect when backup jobs launch. This opportunistic approach providesadded flexibility and robustness to the process of backing up log files,and also provides information that may be useful to operators inre-configuring the system.

In addition to the adaptive behavior, the illustrative system also mayreport on threshold conditions so that system operators may takecorrective action as deemed appropriate. For example, if it appears thatfactor 401 on disk space usage frequently exceeds its threshold andkicks off too many backup jobs, system operators may increase theallocated disk space or move the log file to a different disk drive.Thus, on one hand, system operators may rely on the system's ownadaptive techniques to manage log file backups with relatively little orno intervention; on the other hand, system operators may detect systemicconfiguration problems based on the backup-readiness operational factorsand may then re-configure certain components as they see fit.

An exemplary data set is illustrated in Table 1 below. For example, in acase where ten (10) backup jobs occurred since the last evaluation, thebackup-readiness operational factors and their assigned weights mightlook like the table below. For simplicity, factors 402 and 405 are notused in this example. Table 1 is presented here for illustrativepurposes. Other factors, thresholds, and normalization schemes may bechosen, depending on the technology and the behavior of the implementedsystem.

Table 1 appears below:

TABLE 1 Illustrative data set for ten log file backup jobs. FactorFactor Factor Factor Factor Factor 401: 402 403: % 404: 405 disk space(not elapsed of idle (not usage % used) threshold CPU % used) Thresh-67% 24 hours 59% idle old Value Weight W1 = W3 =  W4 = 40% 30% 30% JobID 1   70% * 1 hr = 1/24 70% * 2   80% * 2 hr = 1/12 60% * 3   80% * 4hr = ⅙  40%   4 50% 6 hr = ¼  90% * 5 40% 12 hr = ½   90% * 6   70% * 25 hr = 1 1/24 * 90% * 7   80% *  25 hr = 1 1/24 * 50%   8 60% 2 hr =1/12 60% * 9 50% 4 hr = ⅙  90% * 10  60% 2 hr = 1/12 90% * Most- IdleRele- CPU % vant Factor

In Table 1 above, for each log file backup job, the factor(s) thatexceeded their respective threshold when the job was initiated is/areshown with an asterisk (*). In the example of Table 1, the factor thatmost frequently exceeded its threshold in the ten jobs is the idle CPUpercentage (factor 404), which exceeded its threshold in eight of theten jobs. Accordingly, data agent 242 designates idle CPU percentagefactor 404 the most relevant factor for purposes of the illustrativemethod. This designation plays a role in the next block.

At block 605, data agent 242 may increase the weight assigned to thediscovered most-relevant factor(s). Accordingly, data agent 242 mayincrease the weight W4 of factor 404 from 30% to 32%, in an illustrativeincrement.

At block 607, data agent 242 may adjust other factors' respectiveweights, based on the preceding increase. Therefore, illustratively, therelative weights of the other factors will decrease, such that W1 willdrop to 39% and W3 will drop to 29%. As a result of these adjustments,the backup readiness score will more heavily skew to the idle CPU factor404 in future iterations, which may cause more backup jobs to beinitiated when the CPU utilization is relatively low.

At block 609, data agent 242 may prepare to apply the adjusted factorweights in the next cycle, e.g., in monitoring block 305 when the backupreadiness score may be generated. Accordingly, the adjusted weights maybe stored to an appropriate data structure maintained by data agent 242,e.g., a local cache, a file in primary storage, etc. After block 609completes, block 311 may end and control may return to block 305 for anew monitoring cycle using the adjusted weights, as shown in FIG. 3.

In regard to the components, blocks, operations and/or sub-operationsdescribed in reference to FIGS. 2-6, other embodiments are possiblewithin the scope of the present invention, such that the above-recitedcomponents, steps, blocks, operations, and/ormessages/requests/queries/instructions are differently arranged,sequenced, sub-divided, organized, and/or combined. In some embodiments,a different component may initiate or execute a given operation.

For example, in some alternative embodiments, data agent 242 may notifystorage manager 240 that a backup readiness score exceeds theoperational threshold; storage manager 240 may then take over controland initiate and manage a log file backup job. Moreover, the secondarycopy operations are not limited to a backup job; for example, archivecopies, reference copies, with or without deduplication and/orencryption and/or compression and/or content classification etc. alsomay be created based on a job initiated opportunistically as describedherein.

EXAMPLE EMBODIMENTS

An illustrative embodiment may comprise a storage management system foropportunistically initiating a backup job based on a backup readinessscore instead of based on a pre-defined schedule, the storage managementsystem comprising: a client computing device comprising a databaseapplication and an associated data agent; a primary storage device incommunication with the client computing device, the primary storagedevice comprising a log file populated by the database application; anda secondary storage device comprising a secondary copy of the log file;wherein the data agent is configured to: monitor a plurality ofoperational factors associated with at least one of the log file and thedatabase application, generate a backup readiness score based on atleast one of the operational factors exceeding its respective thresholdvalue, and initiate a backup job for the log file based on the backupreadiness score, wherein the secondary copy of the log file is a resultof the backup job.

The above-recited storage management system wherein the backup job lacksa pre-defined schedule and instead the backup job is initiated when thebackup readiness score exceeds a threshold value. The above-recitedstorage management system wherein the backup readiness score is based onthe plurality of monitored operational factors. The above-recitedstorage management system wherein the backup readiness score is based onthe plurality of monitored operational factors, and is further based ona weight assigned to each respective operational factor. Theabove-recited storage management system wherein the backup readinessscore is based on the plurality of monitored operational factors, and isfurther based on a weight assigned to each respective operational factorbased on an evaluation of a plurality of backup jobs executed since apreceding evaluation. The above-recited storage management systemwherein the backup job is initiated when the backup readiness scoreexceeds a threshold value.

The above-recited storage management system wherein the data agent isfurther configured to: adjust at least one weight assigned to acorresponding operational factor in the plurality of operationalfactors, based on an evaluation of a plurality of backup jobs executedsince a preceding evaluation. The above-recited storage managementsystem wherein a second backup job for the log file is based on a secondbackup readiness score which is based on an increased weight for a firstoperational factor in the plurality of operational factors, wherein theincreased weight results from an evaluation of a plurality of executedbackup jobs executed since a preceding evaluation. The above-recitedstorage management system wherein a second backup job for the log fileis based on a second backup readiness score which is based on anincreased weight for a first operational factor in the plurality ofoperational factors, wherein the increased weight results from anevaluation of a plurality of executed backup jobs executed since apreceding evaluation, and wherein in the plurality of executed backupjobs the first operational factor most often, relative to the otheroperational factors, exceeded its respective threshold value. Theabove-recited storage management system further comprising: a mediaagent associated with the secondary storage device, wherein the mediaagent is configured to store the secondary copy of the log file to thesecondary storage device.

The above-recited storage management system wherein the plurality ofoperational factors comprises at least one of: (i) a measure of theamount of storage space occupied by the log file; (ii) a measure of theamount of storage space occupied by the log file since a precedingbackup job was initiated; (iii) a number of log file entries generatedsince the preceding backup job; (iv) a number of database applicationtransactions executed since the preceding backup job was initiated; (v)a measure of elapsed time since the preceding backup job was initiated;(vi) a measure of activity of the database application during a periodof time; (vii) a measure of usage of the primary storage device during aperiod of time; (viii) a measure of usage, by the database application,of the primary storage device during a period of time; and (ix) ameasure of usage of the client computing device during a period of time.The above-recited storage management system wherein the plurality ofoperational factors comprises a vendor-specific parameter associatedwith at least one of the database application and the primary storagedevice. The above-recited storage management system wherein theplurality of operational factors comprises a version-specific parameterassociated with the database application. The above-recited storagemanagement system wherein the system further comprises a storage managerfor managing the backup job. The above-recited storage management systemwherein the backup job comprises at least one of: a secondary copyoperation, a deduplication operation, an encryption operation, acompression operation.

Another, alternative embodiment may comprise a system foropportunistically initiating a backup job based on a backup readinessscore instead of based on a pre-defined schedule, the system comprising:a client computing device comprising a database application and anassociated data agent; a primary storage device in communication withthe client computing device, the primary storage device comprising a logfile populated by the database application; and a secondary storagedevice comprising a secondary copy of the log file; wherein the dataagent is configured to: monitor a plurality of operational factorsassociated with at least one of the log file and the databaseapplication, generate a first backup readiness score that is based onthe plurality of monitored operational factors, and initiate a firstbackup job for the log file based on the backup readiness score, whereinthe secondary copy of the log file is a result of the first backup job;and wherein the data agent is further configured to: evaluate aplurality of executed backup jobs that includes the first backup job,wherein in the plurality of executed backup jobs a first operationalfactor most often, relative to the other operational factors, exceededits respective threshold value, and initiate a second backup job of thelog file based on a second backup readiness score which is based on anincreased weight for the first operational factor, wherein the increasedweight results from the evaluation of the plurality of executed backupjobs.

The above-recited system wherein the first backup readiness score isgenerated based on at least one of the operational factors exceeding itsrespective threshold value. The above-recited system wherein the firstbackup job is initiated when the backup readiness score exceeds athreshold value. The above-recited system wherein the data agent isfurther configured to: increase the weight for the first operationalfactor, and decrease a second weight for a corresponding secondoperational factor in the plurality of operational factors, wherein thedecrease also results from the evaluation of the plurality of executedbackup jobs. The above-recited system wherein the first backup job isinitiated when the first backup readiness score exceeds a thresholdvalue, and further wherein the second backup job is initiated when thesecond backup readiness score exceeds the threshold value.

An alternative embodiment may comprise a system for opportunisticallygenerating one or more secondary copies of a file based on a readinessscore instead of based on a pre-defined schedule, the system comprising:a client computing device comprising an executable component and anassociated data agent; a first storage device in communication with theclient computing device, the primary storage device comprising a filepopulated at least in part by the executable component; and a secondstorage device comprising a secondary copy of the file; wherein the dataagent is configured to: monitor a plurality of operational factorsassociated with at least one of the file and the executable component,generate a readiness score based on at least one of the operationalfactors exceeding its respective threshold value, and initiate asecondary copy operation for the file based on the readiness score,wherein the secondary copy of the log file is a result of the secondarycopy operation.

The above-recited system wherein the executable component is at leastone of an application, an operating system, a file system, and a virtualmachine. The above-recited system wherein the file comprises atransaction log of the executable component. The above-recited systemwherein the secondary copy operation lacks a pre-defined schedule andinstead is initiated when the readiness score passes a threshold value.The above-recited system wherein the readiness score is based on theplurality of monitored operational factors. The above-recited systemwherein the readiness score is based on the plurality of monitoredoperational factors, and is further based on a weight assigned to eachrespective operational factor. The above-recited system wherein thereadiness score is based on the plurality of monitored operationalfactors, and is further based on a weight assigned to each respectiveoperational factor based on an evaluation of a plurality of secondarycopy operations for the file executed since a preceding evaluation. Theabove-recited system wherein the secondary copy operation is initiatedwhen the readiness score exceeds a threshold value. The above-recitedsystem wherein the data agent is further configured to: adjust at leastone weight assigned to a corresponding operational factor in theplurality of operational factors, based on an evaluation of a pluralityof secondary copy operations executed since a preceding evaluation. Theabove-recited system wherein a second backup job for the log file isbased on a second backup readiness score which is based on an increasedweight for a first operational factor in the plurality of operationalfactors, wherein the increased weight results from an evaluation of aplurality of executed backup jobs executed since a preceding evaluation.The above-recited system wherein a second backup job for the log file isbased on a second backup readiness score which is based on an increasedweight for a first operational factor in the plurality of operationalfactors, wherein the increased weight results from an evaluation of aplurality of executed backup jobs executed since a preceding evaluation,and wherein in the plurality of executed backup jobs the firstoperational factor most often, relative to the other operationalfactors, exceeded its respective threshold value. The above-recitedsystem further comprising: a media agent associated with the secondarystorage device, wherein the media agent is configured to store thesecondary copy of the log file to the secondary storage device.

Another exemplary embodiment may comprise a system for opportunisticallygenerating secondary copies of a file based on a readiness score insteadof based on a pre-defined schedule, the system comprising: a clientcomputing device comprising an executable component and an associateddata agent; a first storage device in communication with the clientcomputing device, the first storage device comprising a file populatedat least in part by executable component; and a second storage devicecomprising a secondary copy of the file; wherein the data agent isconfigured to: monitor a plurality of operational factors associatedwith at least one of the file and the executable component, generate afirst readiness score that is based on the plurality of monitoredoperational factors, and generate a first secondary copy of the filebased on the readiness score; and wherein the data agent is furtherconfigured to: evaluate a plurality of executed secondary copyoperations, wherein in the plurality of executed secondary copyoperations a first operational factor most often, relative to the otheroperational factors, exceeded its respective threshold value, andgenerate a second secondary copy of the log file based on a secondreadiness score which is based on an increased weight for the firstoperational factor, wherein the increased weight results from theevaluation of the plurality of executed secondary copy operations.

The above-recited system wherein the first readiness score is generatedbased on at least one of the operational factors exceeding itsrespective threshold value. The above-recited system wherein the firstsecondary copy is generated when the readiness score exceeds a thresholdvalue. The above-recited system wherein the data agent is furtherconfigured to: increase the weight for the first operational factor, anddecrease a second weight for a corresponding second operational factorin the plurality of operational factors, wherein the decrease alsoresults from the evaluation of the plurality of executed secondary copyoperations. The above-recited system wherein the first secondary copy isgenerated when the first readiness score exceeds a threshold value, andfurther wherein the second secondary copy is generated when the secondreadiness score exceeds the threshold value. The above-recited systemwherein the executable component is at least one of an application, anoperating system, a file system, and a virtual machine. Theabove-recited system wherein the file comprises a transaction log of theexecutable component. The above-recited system wherein the secondarycopy operation lacks a pre-defined schedule and instead is initiatedwhen the readiness score passes a threshold value. The above-recitedsystem wherein the readiness score is based on the plurality ofmonitored operational factors, and is further based on a weight assignedto each respective operational factor.

An illustrative embodiment may comprise a method for opportunisticallyinitiating a backup job in a storage management system based on a backupreadiness score, the method comprising: executing a database applicationon a client computing device, wherein the database application populatesat least part of an associated log file; monitoring, by a data agent, aplurality of operational factors associated with at least one of thedatabase application and the log file populated at least in part by thedatabase application; generating, by the data agent, a first backupreadiness score based on the plurality of operational factors;initiating, by the data agent, a first backup job for the log file basedon the backup readiness score, wherein the first backup job generates afirst secondary copy of the log file; evaluating, by the data agent, aplurality of executed backup jobs including the first backup job,wherein in the plurality of backup jobs a first operational factor mostoften exceeded, relative to the other operational factors, itsrespective threshold value; generating, by the data agent, a secondbackup readiness score based on an increased weight for the firstoperational factor, wherein the increased weight results from theevaluating of the plurality of executed backup jobs; and initiating, bythe data agent, a second backup job of the log file based on the secondbackup readiness score, wherein the second backup job generates a secondsecondary copy of the log file.

The above-recited method wherein the first backup readiness score isgenerated when one or more of the operational factors exceeds arespective threshold value. The above-recited method further comprising:based on the evaluating of the plurality of backup jobs, adjusting, bythe data agent, at least one weight associated with a correspondingsecond operational factor in the plurality of operational factors. Theabove-recited method wherein the first backup job is initiated when thefirst backup readiness score exceeds a threshold value. Theabove-recited method wherein the first backup job is initiated when thefirst backup readiness score exceeds a threshold value, and furtherwherein the second backup job is initiated when the second backupreadiness score exceeds the threshold value. The above-recited methodwherein the data agent also executes on the client computing device.

An alternative embodiment may comprise a method for opportunisticallyinitiating a backup job based on a backup readiness score in a storagemanagement system, the method comprising: executing an executablecomponent on a client computing device, wherein the executable componentis associated with a file stored in a primary storage device;monitoring, by a data agent executing on the client computing device, aplurality of operational factors associated with at least one of theexecutable component and the file associated with the executablecomponent; generating, by the data agent, a first backup readiness scorebased on the plurality of operational factors; and initiating, by thedata agent, a first backup job for the file based on the backupreadiness score, wherein the first backup job generates a firstsecondary copy of the file.

The above-recited method may further comprise: evaluating, by the dataagent, a plurality of executed backup jobs including the first backupjob, wherein the evaluating comprises (i) identifying a firstoperational factor which, in the plurality of backup jobs, most often,relative to the other operational factors, exceeded its respectivethreshold value, and further comprises (ii) increasing a weight for thefirst operational factor; generating, by the data agent, a second backupreadiness score based on the increased weight for the first operationalfactor; and initiating, by the data agent, a second backup job of thefile based on the second backup readiness score, wherein the secondbackup job generates a second secondary copy of the file. Theabove-recited method wherein the executable component is a databaseapplication. The above-recited method wherein the executable componentis a database application, and wherein the file comprises a transactionfile populated by the database application.

Another exemplary embodiment may comprise a method for opportunisticallygenerating one or more secondary copies of a file based on a readinessscore in a storage management system, the method comprising: executingan executable component on a client computing device, wherein theexecutable component populates at least part of an associated file;monitoring, by a data agent, a plurality of operational factorsassociated with at least one of the executable component and the file;generating, by the data agent, a first readiness score based on theplurality of operational factors; initiating, by the data agent, a firstsecondary copy operation based on the readiness score, wherein the firstsecondary copy operation generates a first secondary copy of the file;evaluating, by the data agent, a plurality of executed secondary copyoperations including the first secondary copy operation, wherein, in theplurality of executed secondary copy operations, a first operationalfactor most often, relative to the other operational factors, exceededits respective threshold value; generating, by the data agent, a secondreadiness score based on an increased weight for the first operationalfactor, wherein the increased weight results from the evaluating of theplurality of executed secondary copy operations; and initiating, by thedata agent, a second secondary copy operation based on the secondreadiness score, wherein the second secondary copy operation generates asecond secondary copy of the log file.

The above-recited method wherein the first readiness score is generatedwhen one or more of the operational factors exceeds a respectivethreshold value. The above-recited method may further comprise: based onthe evaluating of the plurality of executed secondary copy operations,adjusting, by the data agent, at least one weight assigned to acorresponding second operational factor in the plurality of operationalfactors. The above-recited method wherein the first secondary copyoperation is initiated when the first readiness score exceeds athreshold value. The above-recited method wherein the first secondarycopy operation is initiated when the first readiness score exceeds athreshold value, and further wherein the second secondary copy operationis initiated when the second readiness score exceeds the thresholdvalue. The above-recited method wherein the first readiness score isgenerated based on at least one of the operational factors exceeding itsrespective threshold value. The above-recited method wherein the firstsecondary copy is generated when the readiness score exceeds a thresholdvalue.

An alternative embodiment may comprise a method comprising: generating afirst secondary copy of a file in a storage management system, whereinthe generating is based on a first backup readiness score instead ofbased on a pre-defined schedule; wherein the method further comprises:executing a database application on a client computing device, whereinthe database application populates at least part of a file; monitoring,by a data agent executing on the client computing device, a plurality ofoperational factors associated with at least one of the databaseapplication and the file; initiating, by the data agent, based on thebackup readiness score, a first backup job which generates the firstsecondary copy of the log file; evaluating, by the data agent, aplurality of executed backup jobs including the first backup job,wherein in the plurality of backup jobs, a first operational factor mostoften, relative to the other operational factors, exceeded itsrespective threshold value; generating, by the data agent, a secondbackup readiness score based on an increased weight for the firstoperational factor, wherein the increased weight results from theevaluating of the plurality of executed backup jobs; and initiating, bythe data agent, based on the second backup readiness score, a secondbackup job of the file wherein the second backup job generates a secondsecondary copy of the file.

The above-recited method wherein the file comprises at least one of: atransaction log file and a database. The above-recited method whereinthe first backup readiness score is generated when one or more of theoperational factors exceeds a respective threshold value. Theabove-recited method may further comprise: based on the evaluating ofthe plurality of backup jobs, adjusting, by the data agent, at least oneweight associated with a corresponding second operational factor in theplurality of operational factors before generating the second backupreadiness score. The above-recited method wherein the first backup jobis initiated when the first backup readiness score exceeds a thresholdvalue. The above-recited method wherein the first backup job isinitiated when the first backup readiness score exceeds a thresholdvalue, and further wherein the second backup job is initiated when thesecond backup readiness score exceeds the threshold value.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof means any connection or coupling,either direct or indirect, between two or more elements; the coupling orconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, refer tothis application as a whole and not to any particular portions of thisapplication. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or” in reference to alist of two or more items, covers all of the following interpretationsof the word: any one of the items in the list, all of the items in thelist, and any combination of the items in the list. Likewise the term“and/or” in reference to a list of two or more items, covers all of thefollowing interpretations of the word: any one of the items in the list,all of the items in the list, and any combination of the items in thelist.

Depending on the embodiment, certain operations, acts, events, orfunctions of any of the algorithms described herein can be performed ina different sequence, can be added, merged, or left out altogether(e.g., not all are necessary for the practice of the algorithms).Moreover, in certain embodiments, operations, acts, functions, or eventscan be performed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described herein. Software and other modulesmay reside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local memory, via a network, via a browser, or via other meanssuitable for the purposes described herein. Data structures describedherein may comprise computer files, variables, programming arrays,programming structures, or any electronic information storage schemes ormethods, or any combinations thereof, suitable for the purposesdescribed herein. User interface elements described herein may compriseelements from graphical user interfaces, interactive voice response,command line interfaces, and other suitable interfaces.

Further, the processing of the various components of the illustratedsystems can be distributed across multiple machines, networks, and othercomputing resources. In addition, two or more components of a system canbe combined into fewer components. Various components of the illustratedsystems can be implemented in one or more virtual machines, rather thanin dedicated computer hardware systems and/or computing devices.Likewise, the data repositories shown can represent physical and/orlogical data storage, including, for example, storage area networks orother distributed storage systems. Moreover, in some embodiments theconnections between the components shown represent possible paths ofdata flow, rather than actual connections between hardware. While someexamples of possible connections are shown, any of the subset of thecomponents shown can communicate with any other subset of components invarious implementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

These computer program instructions may also be stored in anon-transitory computer-readable memory that can direct a computer orother programmable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded onto a computing device or other programmable data processingapparatus to cause a series of operations to be performed on thecomputing device or other programmable apparatus to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide steps for implementingthe acts specified in the flow chart and/or block diagram block orblocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention.

These and other changes can be made to the invention in light of theabove Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesthe various aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for”, but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A storage management system for opportunisticallyinitiating backup jobs based on a backup readiness score instead ofbased on a pre-defined schedule, the system comprising: a clientcomputing device comprising an application and an associated data agent;a first data storage device in communication with the client computingdevice, the first data storage device comprising a log file populated bythe application; and a second data storage device comprising a secondarycopy of the log file; wherein the data agent is configured to: monitor aplurality of operational factors associated with at least one of the logfile and the application, generate a backup-readiness score based on atleast one of the operational factors exceeding a respective thresholdvalue, and initiate a backup job of the log file based on thebackup-readiness score, wherein the secondary copy of the log file is aresult of the backup job; wherein the data agent is further configuredto: increase a weight for a first operational factor among the pluralityof operational factors, based on analyzing a plurality ofpreviously-executed backup jobs, evaluate a second backup-readinessscore which is based on the increased weight, and initiate a secondbackup job of the log file based on the second backup-readiness score.2. The storage management system of claim 1 wherein the plurality ofoperational factors comprises at least one of: (i) a measure of theamount of storage space occupied by the log file; (ii) a measure of theamount of storage space occupied by the log file since a precedingbackup job was initiated; (iii) a number of log file entries generatedsince the preceding backup job; (iv) a number of applicationtransactions executed since the preceding backup job was initiated; (v)a measure of elapsed time since the preceding backup was initiated; (vi)a measure of activity of the application during a period of time; (vii)a measure of usage of the first data storage device during a period oftime; (viii) a measure of usage, by the application, of the first datastorage device during a period of time; and (ix) a measure of usage ofthe client computing device during a period of time.
 3. The storagemanagement system of claim 1 wherein a given backup job of the log filelacks a pre-defined schedule and instead the backup job is initiatedwhen an evaluated backup-readiness score exceeds a threshold value. 4.The storage management system of claim 1 wherein a givenbackup-readiness score is based on the plurality of monitoredoperational factors, and is further based on a weight assigned to eachrespective operational factor.
 5. The storage management system of claim1 wherein the plurality of operational factors further comprises amanufacturer-specific parameter associated with at least one of theapplication and the first data storage device.
 6. The storage managementsystem of claim 1 further comprising a storage manager for managing thebackups of the log file, wherein the storage manager instructs the dataagent when to initiate a given backup job.
 7. The storage managementsystem of claim 1 wherein a given backup job comprises at least one of:a secondary copy operation, a deduplication operation, an encryptionoperation, and a compression operation.
 8. A storage management systemfor opportunistically initiating backups based on a backup-readinessscore instead of based on a pre-defined schedule, the system comprising:a client computing device comprising an application and an associateddata agent; a first data storage device in communication with the clientcomputing device, the first data storage device comprising a log filepopulated by the application; and a second data storage devicecomprising a secondary copy of the log file; wherein the data agent isconfigured to: monitor a plurality of operational factors associatedwith at least one of the log file and the application, generate abackup-readiness score based on at least one of the operational factorsexceeding a respective threshold value, and initiate a backup of the logfile based on the backup-readiness score, wherein the secondary copy ofthe log file is a result of the backup; wherein the data agent isfurther configured to: based on evaluating by the data agent of aplurality of executed backups executed since a preceding evaluation,increase a weight for a first operational factor among the plurality ofoperational factors, and initiate a second backup of the log file basedon a second backup-readiness score which is based on the increasedweight; and wherein the plurality of operational factors comprises atleast one of: (i) a measure of the amount of storage space occupied bythe log file; (ii) a measure of the amount of storage space occupied bythe log file since a preceding backup job was initiated; (iii) a numberof log file entries generated since the preceding backup job; (iv) anumber of application transactions executed since the preceding backupjob was initiated; (v) a measure of elapsed time since the precedingbackup was initiated; (vi) a measure of activity of the applicationduring a period of time; (vii) a measure of usage of the first datastorage device during a period of time; (viii) a measure of usage, bythe application, of the first data storage device during a period oftime; and (ix) a measure of usage of the client computing device duringa period of time.
 9. The storage management system of claim 8 wherein agiven backup of the log file lacks a pre-defined schedule and insteadthe backup is initiated when the backup readiness score exceeds athreshold value.
 10. The storage management system of claim 8 wherein agiven backup-readiness score is based on the plurality of monitoredoperational factors, and is further based on a weight assigned to eachrespective operational factor.
 11. The storage management system ofclaim 8 wherein a given backup is initiated when a respectivebackup-readiness score exceeds a threshold value.
 12. The storagemanagement system of claim 8 wherein the data agent is furtherconfigured to: adjust at least one weight assigned to a correspondingoperational factor in the plurality of operational factors, based on theevaluating by the data agent of a plurality of executed backups executedsince a preceding evaluation.
 13. The storage management system of claim8 wherein the plurality of operational factors further comprises amanufacturer-specific parameter associated with at least one of theapplication and the first data storage device.
 14. The storagemanagement system of claim 8 wherein the plurality of operationalfactors further comprises a version-specific parameter associated withthe application.
 15. The storage management system of claim 8 furthercomprising a storage manager for managing the backups of the log file.16. The storage management system of claim 8 wherein a given backupcomprises at least one of: a secondary copy operation, a deduplicationoperation, an encryption operation, and a compression operation.
 17. Acomputer-readable medium, excluding transitory propagating signals,storing instructions that, when executed by at least one computingdevice comprising one or more processors and corresponding computermemory, cause the computing device to perform operations comprising:executing a database application on the computing device, wherein thedatabase application populates at least part of an associated log file;monitoring, by a data agent executing on the computing device, aplurality of operational factors associated with at least one of thedatabase application and the log file populated at least in part by thedatabase application; generating, by the data agent, a first backupreadiness score based on the plurality of operational factors;initiating, by the data agent, a first backup job for the log file basedon the backup readiness score, wherein the first backup job generates afirst secondary copy of the log file; evaluating, by the data agent, aplurality of executed backup jobs including the first backup job,wherein in the plurality of backup jobs a first operational factor mostoften exceeded, relative to the other operational factors, itsrespective threshold value; generating, by the data agent, a secondbackup readiness score based on an increased weight for the firstoperational factor, wherein the increased weight results from theevaluating of the plurality of executed backup jobs; and initiating, bythe data agent, a second backup job of the log file based on the secondbackup readiness score, wherein the second backup job generates a secondsecondary copy of the log file.
 18. The computer-readable medium ofclaim 17 wherein the first backup readiness score is generated when oneor more of the operational factors exceeds a respective threshold value.19. The computer-readable medium of claim 17 further comprising: basedon the evaluating of the plurality of backup jobs, adjusting, by thedata agent, at least one weight associated with a corresponding secondoperational factor in the plurality of operational factors.
 20. Thecomputer-readable medium of claim 17 wherein the first backup job isinitiated when the first backup readiness score exceeds a thresholdvalue, and further wherein the second backup job is initiated when thesecond backup readiness score exceeds the threshold value.